On Dec 17, 2011, at 6:44 AM, sebb <seb...@gmail.com> wrote:

> On 17 December 2011 05:19, Phil Steitz <phil.ste...@gmail.com> wrote:
>> On 12/16/11 12:56 PM, Mark Thomas wrote:
>>> All,
>>> 
>>> There are currently two options for publishing JARs to Maven Central:
>>> 1. scp+rsync via people.a.o
>>> 2. Nexus
>>> 
>>> Personally, my only requirements are:
>>> a) that the JARs reach Maven Central
>>> b) publishing is as simple as running a single script
>> 
>> I would be very interested to know if anyone has figured out a way
>> to fully script Nexus.  AFAIK, Nexus requires that you use the GUI
> 
> I think that's the main advantage or Nexus - makes it difficult to
> accidentally release files.
> This happened at least once in Commons before we started using Nexus.

Only via the release plugin and not following the documented process at the 
time.  Adding GUI steps and more mysterious software *decreases* control.

> 
> AIUI there is a REST interface which could be scripted if one could
> find the docs.
> But I think it would negate one of the main benefits if this allowed
> releases to be published to Maven Central automatically.

Which the simple rsync setup that tomcat and some Commons holdouts still use 
does in a much simpler and more transparent way.
> 
>> and also (sic) store credentials in a plaintext file.  Maybe someone
> 
> AFAIK that's not true - or at least if it is, that's due to using
> Maven deploy, rather than Nexus, which is not directly involved in the
> upload.
> 
>> has figured out a way around this. I would be very interested to
> 
> You can store the master password on a USB stick for Maven to use.
> Or you could use something like a TrueCrypt container file.

Thats what I meant above.

Phil
> 
>> learn this so we can improve the not-quite-functional process that
>> we have been fumbling with in Commons [1]. FWIW, my NSHO is that if
>> you have a working script that produces good artifacts that can be
>> scpd to central, there is no reason to bring in proprietary
>> software, plaintext credential files or GUI steps.
>> 
>> Phil
>> [1] http://wiki.apache.org/commons/UsingNexus
>>> 
>>> I don't particularly care about the details. As long as all I have to do
>>> is run a script and the JARs end up in Maven Central I'm happy. I know
>>> option 1 works and I assume 2 will work the same way. Therefore I have
>>> no preference for either approach.
>>> 
>>> Does anyone else have any requirements / views that would suggest one
>>> approach is better than the other?
>>> 
>>> Mark
>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>> 
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to