[postgis-users] looking for a public well known maven repository for postgis-jdbc 2.1 and later on versions

[Shane StClair]

Sounds good. Any objection to the community manually uploading pre-2.2
versions to Maven Central?

Thanks,
Shane


On Sat, Apr 5, 2014 at 1:38 PM, Paragon Corporation <lr at pcorp.us> wrote:

>  Shane,
> I think we can change our build bot to upload to maven as part of the
> official release job when we build tagged docs etc.  Have to talk over with
> rest of PostGIS psc and dev folks on that.
>
> I guess before that we'll need to completely cleanup the issues with our
> current jdbc which sounds like we are close.  Thanks for the patch BTW.
>
> Thanks,
> Regina Obe
> PostGIS PSC member
> http://www.postgis.us
> http://postgis.net
>
>
>
>  ------------------------------
> *From:* postgis-users-bounces at lists.osgeo.org [mailto:
> postgis-users-bounces at lists.osgeo.org] *On Behalf Of *Shane StClair
> *Sent:* Saturday, April 05, 2014 3:29 PM
> *To:* postgis-users at lists.osgeo.org
> *Subject:* [postgis-users] looking for a public well known maven
> repository for postgis-jdbc 2.1 and later on versions
>
>  I just submitted a patch [1] to generate javadoc and source jars as part
> of the postgis-jdbc build. Otherwise, the existing pom meets the Maven
> Central sync requirements [2].
>
> There are two options for getting up to date postgis-jdbc releases into
> Maven Central. The first would be for Maven Central deployment to become
> part of the postgis release process. After the initial setup the Maven
> Central publishing process isn't terribly painful, but it would require a
> postgis developer to assume responsibility for the Maven Central submission
> and for postgis-jdbc to get special consideration during releases [3] [4].
>
> The other option would be to have the community manually upload to Maven
> Central [5]. This is definitely not the ideal situation, but if Maven
> Central uploads are out of scope for the postgis devs right now it would
> allow us to get updated versions into the central repo. A blessing from the
> postgis devs would help in this second case.
>
> Thanks,
> Shane
>
> [1] http://trac.osgeo.org/postgis/ticket/2702
> [2] https://docs.sonatype.org/display/Repository/Central+Sync+Requirements
> [3]
> https://maven.apache.org/guides/mini/guide-central-repository-upload.html
> [4] http://central.sonatype.org/pages/ossrh-guide.html
> [5]
> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
>
> --
> Shane StClair
> Software Engineer
> Axiom Consulting & Design
> http://www.axiomalaska.com
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>



-- 
Shane StClair
Software Engineer
Axiom Consulting & Design
http://www.axiomalaska.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20140405/c2cdcf08/attachment.html>