<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-9" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 10.00.9200.16866"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial>Baris,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial>Regarding this:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014>> 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 </SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014>> repositories on
trunk.</SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial>+1 for that. Others in PSC and development please vote
on this as well so we can start moving on this.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial>I think we'll be releasing a 2.1.3 fairly soon. 2.2.0 we
are looking at at least another 4 months and that's being hopeful
:)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial>Regina</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial><A
href="http://www.postgis.us">http://www.postgis.us</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial><A
href="http://postgis.net">http://postgis.net</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=994594100-20042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV><FONT color=#0000ff size=2
face=Arial></FONT><BR>
<DIV lang=en-us class=OutlookMessageHeader dir=ltr align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> postgis-users-bounces@lists.osgeo.org
[mailto:postgis-users-bounces@lists.osgeo.org] <B>On Behalf Of </B>Baris
Ergun<BR><B>Sent:</B> Saturday, April 19, 2014 4:50 AM<BR><B>To:</B> PostGIS
Users Discussion<BR><B>Cc:</B> PostGIS Development Discussion<BR><B>Subject:</B>
Re: [postgis-users] [postgis-devel] looking for a public well known maven
repository for postgis-jdbc 2.1 and later on versions<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr>Hi Shane;
<DIV><BR></DIV>
<DIV>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".</DIV>
<DIV><BR></DIV>
<DIV>Baris</DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On 7 April 2014 21:26, Shane StClair <SPAN dir=ltr><<A
href="mailto:shane@axiomalaska.com"
target=_blank>shane@axiomalaska.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV dir=ltr>
<DIV>Hi Baris,</DIV>
<DIV><BR></DIV>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.
<DIV><BR></DIV>
<DIV>Best,</DIV>
<DIV>Shane</DIV></DIV>
<DIV class=HOEnZb>
<DIV class=h5>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Sun, Apr 6, 2014 at 2:29 AM, Baris Ergun <SPAN
dir=ltr><<A href="mailto:barisergun75@gmail.com"
target=_blank>barisergun75@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV dir=ltr>Hi Shane;
<DIV><BR></DIV>
<DIV>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. </DIV>
<DIV><BR></DIV>
<DIV>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.</DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>
<DIV>
<DIV>On 6 April 2014 05:32, Paragon Corporation <SPAN dir=ltr><<A
href="mailto:lr@pcorp.us" target=_blank>lr@pcorp.us</A>></SPAN>
wrote:<BR></DIV></DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV>
<DIV><U></U>
<DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff face=Arial>I don't have
any objections. +1 for that.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
face=Arial>Regina</FONT></SPAN></DIV><BR>
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma>
<DIV><B>From:</B> <A href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A> [mailto:<A
href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A>] <B>On Behalf Of
</B>Shane StClair<BR></DIV><B>Sent:</B> Saturday, April 05, 2014 5:24
PM<BR><B>To:</B> PostGIS Users Discussion<BR><B>Cc:</B> PostGIS
Development Discussion<BR><B>Subject:</B> Re: [postgis-users] looking for
a public well known maven repository for postgis-jdbc 2.1 and later on
versions<BR></FONT><BR></DIV>
<DIV>
<DIV>
<DIV></DIV>
<DIV dir=ltr>Sounds good. Any objection to the community manually
uploading pre-2.2 versions to Maven Central?
<DIV><BR></DIV>
<DIV>Thanks,</DIV>
<DIV>Shane</DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Sat, Apr 5, 2014 at 1:38 PM, Paragon Corporation
<SPAN dir=ltr><<A href="mailto:lr@pcorp.us"
target=_blank>lr@pcorp.us</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><U></U>
<DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
face=Arial>Shane,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff face=Arial>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff face=Arial>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff face=Arial>Regina Obe
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff face=Arial>PostGIS PSC
member</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff face=Arial><A
href="http://www.postgis.us"
target=_blank>http://www.postgis.us</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff face=Arial><A
href="http://postgis.net"
target=_blank>http://postgis.net</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
face=Arial></FONT></SPAN> </DIV><BR>
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma><B>From:</B> <A
href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A> [mailto:<A
href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A>] <B>On Behalf Of
</B>Shane StClair<BR><B>Sent:</B> Saturday, April 05, 2014 3:29
PM<BR><B>To:</B> <A href="mailto:postgis-users@lists.osgeo.org"
target=_blank>postgis-users@lists.osgeo.org</A><BR><B>Subject:</B>
[postgis-users] looking for a public well known maven repository for
postgis-jdbc 2.1 and later on versions<BR></FONT><BR></DIV>
<DIV>
<DIV>
<DIV></DIV>
<DIV dir=ltr>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].
<DIV><BR></DIV>
<DIV>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].</DIV>
<DIV><BR></DIV>
<DIV>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.</DIV>
<DIV><BR></DIV>
<DIV>Thanks,</DIV>
<DIV>Shane
<DIV><BR></DIV>
<DIV>[1] <A href="http://trac.osgeo.org/postgis/ticket/2702"
target=_blank>http://trac.osgeo.org/postgis/ticket/2702</A></DIV>
<DIV>[2] <A
href="https://docs.sonatype.org/display/Repository/Central+Sync+Requirements"
target=_blank>https://docs.sonatype.org/display/Repository/Central+Sync+Requirements</A><BR
clear=all>
<DIV>[3] <A
href="https://maven.apache.org/guides/mini/guide-central-repository-upload.html"
target=_blank>https://maven.apache.org/guides/mini/guide-central-repository-upload.html</A></DIV>
<DIV>[4] <A
href="http://central.sonatype.org/pages/ossrh-guide.html"
target=_blank>http://central.sonatype.org/pages/ossrh-guide.html</A></DIV>
<DIV>[5] <A
href="https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository"
target=_blank>https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository</A></DIV>
<DIV><BR></DIV>-- <BR>Shane StClair<BR>Software Engineer<BR>Axiom
Consulting & Design<BR><A href="http://www.axiomalaska.com"
target=_blank>http://www.axiomalaska.com</A>
</DIV></DIV></DIV></DIV></DIV></DIV><BR>_______________________________________________<BR>postgis-users
mailing list<BR><A href="mailto:postgis-users@lists.osgeo.org"
target=_blank>postgis-users@lists.osgeo.org</A><BR><A
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users"
target=_blank>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</A><BR></BLOCKQUOTE></DIV><BR><BR
clear=all>
<DIV><BR></DIV>-- <BR>Shane StClair<BR>Software Engineer<BR>Axiom
Consulting & Design<BR><A href="http://www.axiomalaska.com"
target=_blank>http://www.axiomalaska.com</A>
</DIV></DIV></DIV></DIV><BR></DIV></DIV>_______________________________________________<BR>postgis-devel
mailing list<BR><A href="mailto:postgis-devel@lists.osgeo.org"
target=_blank>postgis-devel@lists.osgeo.org</A><BR><A
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel"
target=_blank>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel</A><SPAN><FONT
color=#888888><BR></FONT></SPAN></BLOCKQUOTE></DIV><SPAN><FONT
color=#888888><BR><BR clear=all>
<DIV><BR></DIV>-- <BR>
<DIV
dir=ltr>Barış</DIV></FONT></SPAN></DIV><BR>_______________________________________________<BR>postgis-users
mailing list<BR><A href="mailto:postgis-users@lists.osgeo.org"
target=_blank>postgis-users@lists.osgeo.org</A><BR><A
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users"
target=_blank>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</A><BR></BLOCKQUOTE></DIV><BR><BR
clear=all>
<DIV><BR></DIV>-- <BR>Shane StClair<BR>Software Engineer<BR>Axiom Consulting
& Design<BR><A href="http://www.axiomalaska.com"
target=_blank>http://www.axiomalaska.com</A>
</DIV></DIV></DIV><BR>_______________________________________________<BR>postgis-users
mailing list<BR><A
href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</A><BR><A
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users"
target=_blank>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</A><BR></BLOCKQUOTE></DIV><BR><BR
clear=all>
<DIV><BR></DIV>-- <BR>
<DIV dir=ltr>Barış</DIV></DIV></BODY></HTML>