[gdal-dev] gdal jar in maven central

[Justin Deoliveira]

Update on this one. I've created a pull request with the changes to the
java binding build needed to create maven artifacts that meet maven central
requirements.

  https://github.com/OSGeo/gdal/pull/52

I've also started the process of setting up the deployment infrastructure.
Progress is being tracked here:

  https://issues.sonatype.org/browse/OSSRH-14781


Once that is set up I will follow up with some additional instructions to
HOWTO-RELEASE that describe how to deploy maven artifacts.

-Justin

On Tue, Mar 31, 2015 at 10:41 AM, Even Rouault <even.rouault at spatialys.com>
wrote:

> Le mardi 31 mars 2015 18:29:18, Justin Deoliveira a écrit :
> > On Tue, Mar 31, 2015 at 10:01 AM, Even Rouault <
> even.rouault at spatialys.com>
> >
> > wrote:
> > > > Right, there are a few steps involved. The easiest vector that I have
> > >
> > > seen
> > >
> > > > for open source projects  is to utilize the Sonatype OSSRH
> repositories
> > > > (which provide sync to maven central). The full process is described
> > >
> > > here.
> > >
> > > >
> http://central.sonatype.org/pages/ossrh-guide.html#review-requirement
> > > >   s
> > > >
> > > > To sum it up though, here is what I think would be required for gdal.
> > > >
> > > > 1. Create a pom for the gdal jar that adheres to these requirements:
> > > >
> > > >
> > > >
> http://central.sonatype.org/pages/requirements.html#sufficient-metadata
> > > >
> > > > 2. Have a developer set up an OSSRH account and do the initial setup.
> > > >
> > > >
> http://central.sonatype.org/pages/ossrh-guide.html#initial-setup
> > > >
> > > > 3. For each release build the gdal jar (along with it's source and
> > >
> > > javadoc
> > >
> > > > artifacts) and GPG sign them.
> > >
> > >
> http://central.sonatype.org/pages/requirements.html#sign-files-with-gpgpg
> > > p
> > >
> > > >    Then deploy all the jars/signatures to the OSSRH staging
> > > >    repositories.
> > > >
> > > > This will eventually sync them to maven central.
> > > >
> > > >
> > > > Again I'm happy to volunteer to do these steps if there aren't any
> > > > developers on the project that want the extra hassle. Do the java
> > >
> > > bindings
> > >
> > > > have a dedicated maintainer at this point?
> > >
> > > I've somehow taken that hat on, but I've currently no real incentive to
> > > do work in the Java area, so I'm happy if you want to take care of that
> > > aspect.
> > > Beyond the initial setup, it would be great if the steps that need to
> be
> > > taken
> > > at each release are documented in our HOWTO-RELEASE document (at the
> root
> > > of
> > > the source tree) so that anyone not familiar with Java/maven/Sonatype
> > > OSSRH can follow the steps in a rather brainless mode.
> > >
> > > Sure thing. I haven't done much with swig or anything aside from
> > > compiling
> >
> > the bindings, but happy to learn as tasks come up.
> >
> > So how about for a start I work toward deploying the latest stable
> release
> > (1.11.2) jar into maven central. As part of that process I'll document
> the
> > steps required and prepare a patch for HOWTO-RELEASE. Will that work?
>
> Sounds good.
>
> >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Even
> > > > > > >
> > > > > > > --
> > > > > > > Spatialys - Geospatial professional services
> > > > > > > http://www.spatialys.com
> > > > >
> > > > > --
> > > > > Spatialys - Geospatial professional services
> > > > > http://www.spatialys.com
> > >
> > > --
> > > Spatialys - Geospatial professional services
> > > http://www.spatialys.com
>
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20150331/c94539ce/attachment.html>