[Proj4j] Upload to Maven central

[Martin Davis]

All sounds excellent, Tom.  Carry on with the one-time upload!

On Tue, Feb 3, 2015 at 5:13 PM, Tom Arnold <tom9729 at gmail.com> wrote:

> > Is keeping the lib updated an ongoing manual process, or can it be
> automated as part of a build?
>
> 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 (
> http://docs.travis-ci.com/user/getting-started/) 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).
>
> > 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...
>
> Pretty much!
>
> 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.
>
> 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.
>
> Thanks,
> Tom
>
> On Tue, Feb 3, 2015 at 12:32 AM, Martin Davis <mtnclimb at gmail.com> wrote:
>
>> Happy for you to do it!
>>
>> 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...
>>
>>
>>
>>
>>
>> On Mon, Feb 2, 2015 at 8:53 PM, Tom Arnold <tom9729 at gmail.com> wrote:
>>
>>> Martin,
>>>
>>> I've never done it, but it looks like it should be pretty
>>> straightforward. Sonatype has a guide here:
>>> http://central.sonatype.org/pages/ossrh-guide.html
>>>
>>> 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.
>>>
>>> Do you want me to go ahead and do this, or would you rather take care of
>>> it?
>>>
>>> Thanks!
>>> Tom
>>>
>>> On Mon, Feb 2, 2015 at 11:22 PM, Martin Davis <mtnclimb at gmail.com>
>>> wrote:
>>>
>>>> Seems like a great idea!  What's involved with doing this?
>>>>
>>>> On Mon, Feb 2, 2015 at 6:11 PM, Tom Arnold <tom9729 at gmail.com> wrote:
>>>>
>>>>> Is there any plan to upload the current version of proj4j to Maven
>>>>> central?
>>>>>
>>>>> This would make it easier to use in projects that cannot easily add
>>>>> 3rdparty repos.
>>>>>
>>>>> I'm willing to help out if possible.
>>>>>
>>>>> Thanks!
>>>>> Tom
>>>>>
>>>>> _______________________________________________
>>>>> Proj4j mailing list
>>>>> Proj4j at lists.osgeo.org
>>>>> http://lists.osgeo.org/mailman/listinfo/proj4j
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj4j/attachments/20150203/34ec2364/attachment.html>