<!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=710585903-26042014><FONT color=#0000ff
size=2 face=Arial>Baris,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial>Yes we do have a continuous integration bot. Do you have
a script I can schedule her to run or is what is running so far
okay.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial>Currently have this job which runs for
jdbc. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial><A
href="http://debbie.postgis.net:8080/view/PostGIS/job/PostGIS_2.1_JDBC/">http://debbie.postgis.net:8080/view/PostGIS/job/PostGIS_2.1_JDBC/</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial> As far as I can tell last run was
successful</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial><A
href="http://debbie.postgis.net:8080/view/PostGIS/job/PostGIS_2.1_JDBC/558/console">http://debbie.postgis.net:8080/view/PostGIS/job/PostGIS_2.1_JDBC/558/console</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial>If you do have a script, just commit it to this
folder:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial><A
href="http://trac.osgeo.org/postgis/browser/buildbots/debian/scripts">http://trac.osgeo.org/postgis/browser/buildbots/debian/scripts</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial>(I don't have all her scripts in subversion yet but is on my
todo)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial>Regina</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=710585903-26042014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV><BR>
<DIV lang=en-us class=OutlookMessageHeader dir=ltr align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> postgis-devel-bounces@lists.osgeo.org
[mailto:postgis-devel-bounces@lists.osgeo.org] <B>On Behalf Of </B>Baris
Ergun<BR><B>Sent:</B> Friday, April 25, 2014 4:53 PM<BR><B>To:</B> PostGIS
Development Discussion<BR><B>Subject:</B> Re: [postgis-devel] PSC/Development
Vote -- Baris to release upcoming 2.1.3 jars and manually
sign<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr>Completed the task and tested the building of artifacts on
branches/2.1 basically now we have separate jdbc and jdbc_jtsparser projects
(which must be built consecutively). Do we have an continuous integration server
where I can integrate? Otherwise I will have to ask for your help on
verification.</DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On 24 April 2014 13:41, 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>Okey than will start soon.</DIV>
<DIV class=gmail_extra>
<DIV>
<DIV class=h5><BR><BR>
<DIV class=gmail_quote>On 22 April 2014 22:38, Paul Ramsey <SPAN
dir=ltr><<A href="mailto:pramsey@cleverelephant.ca"
target=_blank>pramsey@cleverelephant.ca</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">make
it so +1<BR>
<DIV>
<DIV><BR>On Sat, Apr 19, 2014 at 5:52 PM, Bborie Park <<A
href="mailto:dustymugs@gmail.com" target=_blank>dustymugs@gmail.com</A>>
wrote:<BR>> +1 for release of 2.1.3 jar.<BR>><BR>><BR>> On Sat,
Apr 19, 2014 at 5:47 PM, Paragon Corporation <<A
href="mailto:lr@pcorp.us" target=_blank>lr@pcorp.us</A>>
wrote:<BR>>><BR>>> Baris,<BR>>><BR>>> Regarding
this:<BR>>><BR>>> > Here is my proposal: I can take care of
the last targeted 2.1 release<BR>>> > which is 2.1.3 and
change pom.xmls as I did in the trunk and apply shanes<BR>>> >
patches and after the release of 2.1.3 I can manually sign the jars
and<BR>>> > submit them to OSSRH. And keep discussing the
separation of<BR>>> > repositories on
trunk.<BR>>><BR>>> +1 for that. Others in PSC and
development please vote on this as well so<BR>>> we can start moving
on this.<BR>>><BR>>> I think we'll be releasing a 2.1.3 fairly
soon. 2.2.0 we are looking at<BR>>> at least another 4 months
and that's being hopeful :)<BR>>><BR>>> Thanks,<BR>>>
Regina<BR>>> <A href="http://www.postgis.us"
target=_blank>http://www.postgis.us</A><BR>>> <A
href="http://postgis.net"
target=_blank>http://postgis.net</A><BR>>><BR>>><BR>>>
________________________________<BR>>> From: <A
href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A><BR>>>
[mailto:<A href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A>] On Behalf Of Baris
Ergun<BR>>> Sent: Saturday, April 19, 2014 4:50 AM<BR>>> To:
PostGIS Users Discussion<BR>>> Cc: PostGIS Development
Discussion<BR>>> Subject: Re: [postgis-users] [postgis-devel] looking
for a public well<BR>>> known maven repository for postgis-jdbc 2.1
and later on versions<BR>>><BR>>> Hi
Shane;<BR>>><BR>>> People are busy with other stuff so until we
decide to separate the<BR>>> repositories for postgis java projects I
have applied ur patches to both<BR>>> jdbc and jdbc_jtsparser
projects. So what this means is "when we release<BR>>> 2.2.0 postgis I
would be ready to submit these two jars manually to
OSSRH".<BR>>><BR>>> Baris<BR>>><BR>>><BR>>> On
7 April 2014 21:26, Shane StClair <<A href="mailto:shane@axiomalaska.com"
target=_blank>shane@axiomalaska.com</A>>
wrote:<BR>>>><BR>>>> Hi
Baris,<BR>>>><BR>>>> Oops, I didn't see that you were
already chasing this down. Your approach<BR>>>> sounds great,
thanks for taking the lead on this! In the past there have<BR>>>>
been issues with other projects having non-resolvable dependencies
on<BR>>>> versions of postgis-jdbc (Hibernate Spatial), so it will
be great to have<BR>>>> these artifacts in the central
repo.<BR>>>><BR>>>> Best,<BR>>>>
Shane<BR>>>><BR>>>><BR>>>> On Sun, Apr 6, 2014 at
2:29 AM, Baris Ergun <<A href="mailto:barisergun75@gmail.com"
target=_blank>barisergun75@gmail.com</A>><BR>>>>
wrote:<BR>>>>><BR>>>>> Hi
Shane;<BR>>>>><BR>>>>> Thanks for ur patch and
consideration. I think we are on the same path<BR>>>>> if u
check the issue #2626. I have applied the OSSRH and got the
credentials<BR>>>>> for being able to upload postgis jdbc jars
to central maven rep. For that<BR>>>>> case I have separated the
jdbc and jdbc-jtsparser jars on the trunk and<BR>>>>> updated
the pom.xml's according to Central maven repository
requirements..<BR>>>>> On the trunk actually I was waiting to
agree with all the developers to<BR>>>>> separate the
postgis jdbc jars repository and continue with 1st
suggested<BR>>>>> approach. If we do that way we wouldnt
need to make the explicit plugin<BR>>>>> declarations as you
patched in 2702.<BR>>>>><BR>>>>> Here is my
proposal: I can take care of the last targeted 2.1
release<BR>>>>> which is 2.1.3 and change pom.xmls as I did in
the trunk and apply shanes<BR>>>>> patches and after the release
of 2.1.3 I can manually sign the jars and<BR>>>>> submit them to
OSSRH. And keep discussing the separation of repositories
on<BR>>>>>
trunk.<BR>>>>><BR>>>>><BR>>>>> On 6
April 2014 05:32, Paragon Corporation <<A href="mailto:lr@pcorp.us"
target=_blank>lr@pcorp.us</A>>
wrote:<BR>>>>>><BR>>>>>> I don't have any
objections. +1 for
that.<BR>>>>>><BR>>>>>>
Thanks,<BR>>>>>>
Regina<BR>>>>>><BR>>>>>>
________________________________<BR>>>>>> From: <A
href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A><BR>>>>>>
[mailto:<A href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A>] On Behalf Of Shane
StClair<BR>>>>>> Sent: Saturday, April 05, 2014 5:24
PM<BR>>>>>> To: PostGIS Users
Discussion<BR>>>>>> Cc: PostGIS Development
Discussion<BR>>>>>> Subject: Re: [postgis-users] looking for
a public well known maven<BR>>>>>> repository for
postgis-jdbc 2.1 and later on
versions<BR>>>>>><BR>>>>>> Sounds good. Any
objection to the community manually uploading
pre-2.2<BR>>>>>> versions to Maven
Central?<BR>>>>>><BR>>>>>>
Thanks,<BR>>>>>>
Shane<BR>>>>>><BR>>>>>><BR>>>>>>
On Sat, Apr 5, 2014 at 1:38 PM, Paragon Corporation <<A
href="mailto:lr@pcorp.us"
target=_blank>lr@pcorp.us</A>><BR>>>>>>
wrote:<BR>>>>>>><BR>>>>>>>
Shane,<BR>>>>>>> I think we can change our build bot to
upload to maven as part of the<BR>>>>>>> official release
job when we build tagged docs etc. Have to talk over
with<BR>>>>>>> rest of PostGIS psc and dev folks on
that.<BR>>>>>>><BR>>>>>>> I guess before
that we'll need to completely cleanup the issues
with<BR>>>>>>> our current jdbc which sounds like we are
close. Thanks for the patch
BTW.<BR>>>>>>><BR>>>>>>>
Thanks,<BR>>>>>>> Regina Obe<BR>>>>>>>
PostGIS PSC member<BR>>>>>>> <A
href="http://www.postgis.us"
target=_blank>http://www.postgis.us</A><BR>>>>>>> <A
href="http://postgis.net"
target=_blank>http://postgis.net</A><BR>>>>>>><BR>>>>>>><BR>>>>>>><BR>>>>>>>
________________________________<BR>>>>>>> From: <A
href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A><BR>>>>>>>
[mailto:<A href="mailto:postgis-users-bounces@lists.osgeo.org"
target=_blank>postgis-users-bounces@lists.osgeo.org</A>] On Behalf Of Shane
StClair<BR>>>>>>> Sent: Saturday, April 05, 2014 3:29
PM<BR>>>>>>> To: <A
href="mailto:postgis-users@lists.osgeo.org"
target=_blank>postgis-users@lists.osgeo.org</A><BR>>>>>>>
Subject: [postgis-users] looking for a public well known
maven<BR>>>>>>> repository for postgis-jdbc 2.1 and later
on versions<BR>>>>>>><BR>>>>>>> I just
submitted a patch [1] to generate javadoc and source jars
as<BR>>>>>>> part of the postgis-jdbc build. Otherwise,
the existing pom meets the Maven<BR>>>>>>> Central sync
requirements [2].<BR>>>>>>><BR>>>>>>>
There are two options for getting up to date postgis-jdbc
releases<BR>>>>>>> into Maven Central. The first would be
for Maven Central deployment to<BR>>>>>>> become part of
the postgis release process. After the initial setup
the<BR>>>>>>> Maven Central publishing process isn't
terribly painful, but it would<BR>>>>>>> require a postgis
developer to assume responsibility for the Maven
Central<BR>>>>>>> submission and for postgis-jdbc to get
special consideration during releases<BR>>>>>>> [3]
[4].<BR>>>>>>><BR>>>>>>> The other
option would be to have the community manually upload
to<BR>>>>>>> Maven Central [5]. This is definitely not the
ideal situation, but if Maven<BR>>>>>>> Central uploads
are out of scope for the postgis devs right now it
would<BR>>>>>>> allow us to get updated versions into the
central repo. A blessing from the<BR>>>>>>> postgis devs
would help in this second
case.<BR>>>>>>><BR>>>>>>>
Thanks,<BR>>>>>>>
Shane<BR>>>>>>><BR>>>>>>> [1] <A
href="http://trac.osgeo.org/postgis/ticket/2702"
target=_blank>http://trac.osgeo.org/postgis/ticket/2702</A><BR>>>>>>>
[2]<BR>>>>>>> <A
href="https://docs.sonatype.org/display/Repository/Central+Sync+Requirements"
target=_blank>https://docs.sonatype.org/display/Repository/Central+Sync+Requirements</A><BR>>>>>>>
[3]<BR>>>>>>> <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><BR>>>>>>>
[4] <A href="http://central.sonatype.org/pages/ossrh-guide.html"
target=_blank>http://central.sonatype.org/pages/ossrh-guide.html</A><BR>>>>>>>
[5]<BR>>>>>>> <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><BR>>>>>>><BR>>>>>>>
--<BR>>>>>>> Shane StClair<BR>>>>>>>
Software Engineer<BR>>>>>>> Axiom Consulting &
Design<BR>>>>>>> <A href="http://www.axiomalaska.com"
target=_blank>http://www.axiomalaska.com</A><BR>>>>>>><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>>>>>><BR>>>>>><BR>>>>>><BR>>>>>><BR>>>>>>
--<BR>>>>>> Shane StClair<BR>>>>>> Software
Engineer<BR>>>>>> Axiom Consulting &
Design<BR>>>>>> <A href="http://www.axiomalaska.com"
target=_blank>http://www.axiomalaska.com</A><BR>>>>>><BR>>>>>>
_______________________________________________<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><BR>>>>><BR>>>>><BR>>>>><BR>>>>><BR>>>>>
--<BR>>>>> Barış<BR>>>>><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>>>><BR>>>><BR>>>><BR>>>><BR>>>>
--<BR>>>> Shane StClair<BR>>>> Software
Engineer<BR>>>> Axiom Consulting & Design<BR>>>> <A
href="http://www.axiomalaska.com"
target=_blank>http://www.axiomalaska.com</A><BR>>>><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>>><BR>>><BR>>><BR>>><BR>>>
--<BR>>> Barış<BR>>><BR>>>
_______________________________________________<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><BR>><BR>><BR>><BR>>
_______________________________________________<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><BR>_______________________________________________<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></DIV></DIV></BLOCKQUOTE></DIV><BR><BR
clear=all>
<DIV><BR></DIV></DIV></DIV><SPAN class=HOEnZb><FONT color=#888888>-- <BR>
<DIV dir=ltr>Barış</DIV></FONT></SPAN></DIV></BLOCKQUOTE></DIV><BR><BR
clear=all>
<DIV><BR></DIV>-- <BR>
<DIV dir=ltr>Barış</DIV></DIV></BODY></HTML>