<div dir="ltr">Hi;<div><br></div><div>Only that jdbc_jtsparser project can also be added to Jenkins projects for both branches/2.1 and trunk. No other specific script necessary. (java/jdbc_jtsparser) running 'mvn clean install' on code changes would be enough.</div>
<div><br></div><div>Thanks.</div><div>Baris.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 26 April 2014 07:06, 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="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">Baris,</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">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><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">Currently have this job which runs for
jdbc. </font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"><a href="http://debbie.postgis.net:8080/view/PostGIS/job/PostGIS_2.1_JDBC/" target="_blank">http://debbie.postgis.net:8080/view/PostGIS/job/PostGIS_2.1_JDBC/</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"> As far as I can tell last run was
successful</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"><a href="http://debbie.postgis.net:8080/view/PostGIS/job/PostGIS_2.1_JDBC/558/console" target="_blank">http://debbie.postgis.net:8080/view/PostGIS/job/PostGIS_2.1_JDBC/558/console</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">If you do have a script, just commit it to this
folder:</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"><a href="http://trac.osgeo.org/postgis/browser/buildbots/debian/scripts" target="_blank">http://trac.osgeo.org/postgis/browser/buildbots/debian/scripts</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">(I don't have all her scripts in subversion yet but is on my
todo)</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>
<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>
<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-devel-bounces@lists.osgeo.org" target="_blank">postgis-devel-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:postgis-devel-bounces@lists.osgeo.org" target="_blank">postgis-devel-bounces@lists.osgeo.org</a>] <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<div class=""><br><b>Subject:</b> Re: [postgis-devel] PSC/Development
Vote -- Baris to release upcoming 2.1.3 jars and manually
sign<br></div></font><br></div><div><div class="h5">
<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><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><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></div></div></div>
<br>_______________________________________________<br>
postgis-devel mailing list<br>
<a href="mailto:postgis-devel@lists.osgeo.org">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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">
Barış</div>
</div>