[jsword-devel] Add artifacts to repository?

[Markus Härnvi]

Hi,

On Wed, Nov 24, 2010 at 2:22 PM, Chris Burrell <chris at burrell.me.uk> wrote:

> We do this often at work (set up our own nexus repositories) with free
> software. So if you want I can probably get instructions for setting Nexus
> up (and for Crucible too). Would require a new user to run under probably
> (or perhaps we can run it in the same tomcat instance...)



>


I think it would be less work and less software to maintain if you would use
Sonatypes server. It would have the added benefit that the artifacts would
be synced to the default Maven repo. Developers would not need to add a
special repository.

You would need GnuPG keys for signing. And gpg and Maven is needed on the
build machine and the build.xml needs to be updated.

        /Markus





>
> On 24 November 2010 03:23, Trenton D. Adams <trent at trentonadams.ca> wrote:
>
>> On 10-11-23 04:10 PM, DM Smith wrote:
>>
>>>
>>> On Nov 23, 2010, at 5:11 PM, Markus Härnvi wrote:
>>>
>>>
>>>> Hi,
>>>>
>>>> I looked in the list archives but didn't find a thread about this.
>>>> Sorry if I missed it.
>>>>
>>>> Have there been any discussion on adding JSword jars to the default
>>>> Maven repositories?
>>>>
>>>
>>> Yes. We got the POMs in place. And there was some discussion in
>>>
>>>
>>>> It would help a lot for someone who wants to use JSword in a Maven
>>>> application.
>>>>
>>>
>>> It'd be fine with me, but I know little, almost nothing, about maven.
>>> I'd rather that someone else take on this responsibility. It would be
>>> another mechanism of distribution on top of what we already do.
>>>
>>
>> This is pretty easy.  I don't recommend doing it in the maven repos
>> themselves, as it can be trying I've heard, to get your stuff pushed in
>> right when you want it.  In fact, someone on the maven IRC channel said the
>> same thing.  They recommend that we setup our own repo, and then we can just
>> tell people how to put our repo in their settings.xml.  Then, the jsword
>> docs would simple state two things
>>
>> 1. this is how you setup a dependency in your project, blah, blah, blah
>> 2. this is how you refer to our repo, blah, blah, blah.
>> 2a. in your pom
>> 2b. in your ~/.m2/settings.xml
>>
>> He also mentioned the possible use of a hosted repository for free as
>> Markus mentioned.
>>
>> Anyhow, I'm thinking it wouldn't be difficult to push stuff up to the
>> repo.  I think I had the jar signing working, didn't I?  If so, it would be
>> a simple "mvn deploy" that would do it, I'm thinking, though not positive.
>>
>>
>>>
>>>
>>>> Sonatype is providing free hosting:
>>>>
>>>> http://nexus.sonatype.org/oss-repository-hosting.html
>>>>
>>>> Best regards,
>>>>
>>>> /Markus
>>>>
>>>
>>> In Him,
>>> DM
>>>
>>>
>>>
>>> _______________________________________________
>>> jsword-devel mailing list
>>> jsword-devel at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>>>
>>
>>
>> _______________________________________________
>> jsword-devel mailing list
>> jsword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>>
>
>
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20101124/1369dc1c/attachment-0001.html>