Skip to end of metadata
Go to start of metadata

Motivation:

User list confusion over the number of geotools repositories available during a web search

Contact:

Jody Garnett

Tracker:

http://jira.codehaus.org/browse/GEOT-PENDING

Tagline:

repo where art thou?

Children:

Description

We have published GeoTools, over the years, to any number of different repositories. And then moved on; usually because the repositories cannot handle the strain.

This has resulted in two very interesting things:

How can we fix? Well if you do the same search for geoserver ....

And I see someone has published jts:

Turns out for a brief time geoserver published to codehaus and codehaus mirrors to central and I think Michael Bedward may know something about how jts got published.

So we could do the same - for stable releases.

Reference:

Status

This proposal is stalled waiting for volunteers to sign up to the tasks section.

Voting has not started yet:

Tasks

This section is used to make sure your proposal is complete (did you remember documentation?) and has enough paid or volunteer time lined up to be a success

 

no progress

(tick)

done

(error)

impeded

(warning)

lack mandate/funds/time

(question)

volunteer needed

  1. Check that codehaus still mirrors to maven central
  2. Check for any dependencies that are not in central? (Apparently this is a condition of being published? Except we saw geoserver listed...)
    • We may need to set up geotools library into different groups depending on if they can be published or not? See Split up unsupported modules. That would be sad and probably not worth it - it would amount to us changing the requirements needed in order to be a supported module.
  3. Update the pom.xml to publish to codehaus
  4. Update the instructions
  5. Clean up or mirror old repositories
    • Possibly set up our osgeo org repo as a mirror?
    • Ask refractions to shut off the old repository?
      Or should we not care since it uses "gt2" prefix?

API Changes

BEFORE

trunk/pom.xml

AFTER

Change to codehaus for publication

Documentation Changes

list the pages effected by this proposal

  • No labels

2 Comments

  1. You could also publish directly to central, see Publish to Maven Central Repository

    This is quite simple when using the maven release plugin, you basically need to include the sonatype parent pom as parent for the Geotools parent and assure your credentials are in your local settings.xml file.

  2. I'd be interested in volunteering to help publish the geootools artifacts to Maven Central. I've got experience publishing artifacts via Sonatype to MC. And I've got another project that could use gt as a dependency (wink)