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

Sat Apr 19 01:50:24 PDT 2014

Hi Shane;

People are busy with other stuff so until we decide to separate the
repositories for postgis java projects I have applied ur patches to both
jdbc and jdbc_jtsparser projects. So what this means is "when we release
2.2.0 postgis I would be ready to submit these two jars manually to OSSRH".

Baris

On 7 April 2014 21:26, Shane StClair <shane at axiomalaska.com> wrote:

> Hi Baris,
>
> Oops, I didn't see that you were already chasing this down. Your approach
> sounds great, thanks for taking the lead on this! In the past there have
> been issues with other projects having non-resolvable dependencies on
> versions of postgis-jdbc (Hibernate Spatial), so it will be great to have
> these artifacts in the central repo.
>
> Best,
> Shane
>
>
> On Sun, Apr 6, 2014 at 2:29 AM, Baris Ergun <barisergun75 at gmail.com>wrote:
>
>> Hi Shane;
>>
>> Thanks for ur patch and consideration. I think we are on the same path if
>> u check the issue #2626. I have applied the OSSRH and got the credentials
>> for being able to upload postgis jdbc jars to central maven rep. For that
>> case I have separated the jdbc and jdbc-jtsparser jars on the trunk and
>> updated the pom.xml's according to Central maven repository requirements..
>> On the trunk actually I was waiting to agree  with all the developers to
>> separate the postgis jdbc jars  repository and continue with 1st suggested
>> approach.  If we do that way we wouldnt need to make the explicit plugin
>> declarations as you patched in 2702.
>>
>> Here is my proposal: I can take care of the last  targeted 2.1 release
>> which is 2.1.3 and change pom.xmls as I did in the trunk and apply shanes
>> patches and after the release of 2.1.3 I can manually sign the jars and
>> submit them to OSSRH. And keep discussing the separation of repositories on
>> trunk.
>>
>>
>> On 6 April 2014 05:32, Paragon Corporation <lr at pcorp.us> wrote:
>>
>>>  I don't have any objections.  +1 for that.
>>>
>>> Thanks,
>>> Regina
>>>
>>>  ------------------------------
>>> *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 5:24 PM
>>> *To:* PostGIS Users Discussion
>>> *Cc:* PostGIS Development Discussion
>>> *Subject:* Re: [postgis-users] looking for a public well known maven
>>> repository for postgis-jdbc 2.1 and later on versions
>>>
>>>  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
>>>
>>> _______________________________________________
>>> postgis-devel mailing list
>>> postgis-devel at lists.osgeo.org
>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>>
>>
>>
>>
>> --
>> Barış
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>

-- 
Barış
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20140419/83d29b57/attachment.html>