On 15 November 2011 13:46, Simone Tripodi <simonetrip...@apache.org> wrote:
> Of course, and you find in me one of the artifacts repository supporters! :)
>
> Anyway, I personally prefer to NOT deploy zip/tgz[1] on Nexus to avoid
> manual operations and uploading them to  /dist directly, I found that
> way a little more comfortable.

Still requires a separate manual step to upload the tgz/zip to
somewhere public, but that can be coded as a script.

It would be nice if Nexus automatically released tgz/zip to /dist (I
did ask about that, no plans yet).

Alternatively, dunno whether Commons Parent could be updated to
automatically copy tgz/zip as part of the deploy phase?
Would probably need to be done only as part of a profile, e.g. release.

> Have a nice day, all the best!
> Simo
>
> [1] 
> http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#attach
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Tue, Nov 15, 2011 at 12:56 PM, sebb <seb...@gmail.com> wrote:
>> On 15 November 2011 10:30, Simone Tripodi <simonetrip...@apache.org> wrote:
>>> Hi Gary!
>>> for what I can see, .zip/tar.gz archives were pushed on Nexus - how do
>>> you manage moving them in the right location when the release passes?
>>
>> I've uploaded non-Maven stuff to Nexus in the past - one needs to
>> manually *move* the archives to /dist (i.e. delete from Nexus) before
>> releasing the Maven bits.
>>
>> It's a bit more work for the RM (because currently non-automated), but
>> perhaps easier for reviewers, as only one place to review all the
>> artifacts.
>> And the release of the Maven bits is definitely easier, as Nexus takes
>> care of updating the Maven control files.
>>
>>> I ask just because AFAIK browsing and downloading Nexus with a
>>> non-Maven client, could be blocked... and verifying keys could become
>>> an issue!
>>> Anyway, not being a Nexus expert, for Digester I preferred uploading
>>> on Nexus jars only and used the traditional way for .zip/tar.gz
>>> archives.
>>>
>>> Please let me know, I'd be more than pleased to review the current release!
>>>
>>> All the best,
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Mon, Nov 14, 2011 at 4:31 PM, Gary Gregory <garydgreg...@gmail.com> 
>>> wrote:
>>>> I mean to send that from my @apache.org account, sorry (don't want to
>>>> double send.)
>>>>
>>>> Gary
>>>>
>>>> On Mon, Nov 14, 2011 at 10:30 AM, Gary Gregory 
>>>> <garydgreg...@gmail.com>wrote:
>>>>
>>>>> Good day to you all:
>>>>>
>>>>> I have prepared Commons Codec 1.6-RC1.
>>>>>
>>>>> Tag:
>>>>>
>>>>>
>>>>> https://svn.apache.org/repos/asf/commons/proper/codec/tags/commons-codec-1.6-RC1
>>>>>
>>>>> Site:
>>>>>
>>>>> https://people.apache.org/builds/commons/codec/1.6/RC1/
>>>>>
>>>>> Binaries:
>>>>>
>>>>> https://repository.apache.org/content/repositories/orgapachecommons-181/
>>>>>
>>>>> [ ] +1 release it
>>>>> [ ] +0 go ahead, I cannot take the time
>>>>> [ ] -1 no, do not release it because:
>>>>>
>>>>> This VOTE is open for 72 hours, until November 17 2011, 11:00 EST.
>>>>>
>>>>> Fixed Bugs:
>>>>> o Use standard Maven directory layout.  Issue: CODEC-129. Thanks to
>>>>> ggregory.
>>>>> o Documentation spelling fixes.  Issue: CODEC-128. Thanks to
>>>>> ville.sky...@iki.fi.
>>>>> o Fix various character encoding issues in comments and test cases.
>>>>> Issue: CODEC-127.
>>>>> o ColognePhonetic Javadoc should use HTML entities for special
>>>>> characters.  Issue: CODEC-123.
>>>>>
>>>>> Changes:
>>>>> o Implement a Beider-Morse phonetic matching codec.  Issue: CODEC-125.
>>>>> Thanks to Matthew Pocock.
>>>>> o Migrate to Java 5.  Issue: CODEC-119.
>>>>> o Migrate to JUnit 4.  Issue: CODEC-120.
>>>>>
>>>>> Heads up: the Beider-Morse encoder tests take a long time to run (5
>>>>> minutes). The code has been optimized.
>>>>>
>>>>> Thank you,
>>>>> Gary
>>>>>
>>>>> --
>>>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>>>> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
>>>>> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
>>>>> Blog: http://garygregory.wordpress.com
>>>>> Home: http://garygregory.com/
>>>>> Tweet! http://twitter.com/GaryGregory
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>>> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
>>>> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
>>>> Blog: http://garygregory.wordpress.com
>>>> Home: http://garygregory.com/
>>>> Tweet! http://twitter.com/GaryGregory
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

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

Reply via email to