<div dir="ltr">All sounds excellent, Tom. Carry on with the one-time upload!</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 3, 2015 at 5:13 PM, Tom Arnold <span dir="ltr"><<a href="mailto:tom9729@gmail.com" target="_blank">tom9729@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><span class=""><div>> Is keeping the lib updated an ongoing manual process, or can it be automated as part of a build?<br><br></div></span>I think it can be done either way. My goal for now is to do a one-time upload to get something out there. I'm thinking it will be easier to make it automated once the project moves to GitHub. For example, Travis CI (<a href="http://docs.travis-ci.com/user/getting-started/" target="_blank">http://docs.travis-ci.com/user/getting-started/</a>) is a service integrated with GitHub and does a build for every commit, so you could use this to upload snapshots to central automatically (more on this below).<br></div><span class=""><div><br>> I guess the version # in the pom acts as a unique key, so there's no
problem pushing new versions as long as it is incremented
appropriately...<br><br></div></span>Pretty much!<br><br>A nightly build from trunk would be published as a snapshot; snapshots automatically have a timestamp added to the version to make them unique, and it's considered bad practice to depend on snapshots when you go to do a release. I think Travis CI could be setup to automatically upload these snapshot builds to Maven central. This would be a way for people to get the latest version of the library without building it themselves.<br></div><div><br></div>Every once in awhile someone should cut a release and upload to central. The version number for the release would have to be incremented. I think this can be mostly automated; perhaps by using the maven-release-plugin.</div><div><br></div>Thanks,<br>Tom<br> </div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 3, 2015 at 12:32 AM, Martin Davis <span dir="ltr"><<a href="mailto:mtnclimb@gmail.com" target="_blank">mtnclimb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Happy for you to do it!<div><br></div><div>Is keeping the lib updated an ongoing manual process, or can it be automated as part of a build? I guess the version # in the pom acts as a unique key, so there's no problem pushing new versions as long as it is incremented appropriately...</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 2, 2015 at 8:53 PM, Tom Arnold <span dir="ltr"><<a href="mailto:tom9729@gmail.com" target="_blank">tom9729@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Martin,<br><br>I've never done it, but it looks like
it should be pretty straightforward. Sonatype has a guide here:
<a href="http://central.sonatype.org/pages/ossrh-guide.html" target="_blank">http://central.sonatype.org/pages/ossrh-guide.html</a><br></div><br></div>Basically
you need to make an account and submit a JIRA ticket for proj4j to be
added. Someone will review in a couple of days and then give you access
to upload the library.<br><br></div>Do you want me to go ahead and do this, or would you rather take care of it?<br><br></div>Thanks!<span><font color="#888888"><br>Tom</font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 2, 2015 at 11:22 PM, Martin Davis <span dir="ltr"><<a href="mailto:mtnclimb@gmail.com" target="_blank">mtnclimb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Seems like a great idea! What's involved with doing this?</div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Mon, Feb 2, 2015 at 6:11 PM, Tom Arnold <span dir="ltr"><<a href="mailto:tom9729@gmail.com" target="_blank">tom9729@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div>Is there any plan to upload the current version of proj4j to Maven central?<br><br></div>This would make it easier to use in projects that cannot easily add 3rdparty repos.<br><br></div>I'm willing to help out if possible.<br><br>Thanks!<span><font color="#888888"><br>Tom<br></font></span></div>
<br></div></div>_______________________________________________<br>
Proj4j mailing list<br>
<a href="mailto:Proj4j@lists.osgeo.org" target="_blank">Proj4j@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/proj4j" target="_blank">http://lists.osgeo.org/mailman/listinfo/proj4j</a><br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>