On 28 June 2011 09:52, Simone Tripodi <simonetrip...@apache.org> wrote:
> Hi all guys!!!
> and sorry for the delay - I have no idea why maven artifacts haven't
> been deployed on Nexus; I tried do deploy a SNAPSHOT version and they
> were successfully/automatically deployed on Nexus; once executed the
> release plugin, they were deployed via scp...
> Any hint/suggestion?

Sorry, I've never used the release plugin.

I've only ever used "mvn deploy", which works fine with Nexus - see

http://wiki.apache.org/commons/UsingNexus

> Many thanks in advance, have  anice day!!!
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Tue, Jun 28, 2011 at 8:11 AM, Phil Steitz <phil.ste...@gmail.com> wrote:
>> On 6/27/11 3:11 PM, James Carman wrote:
>>> Should we all be performing releases the same way?  We are one project with
>>> multiple components. We should have a standardized release process.
>>
>> We have common release *requirements* but RMs are free to use the
>> tools that they wish to produce and publish the artifacts.  That has
>> always been the case in Commons.  Tools that make things easier and
>> work get used.  Buggy stuff that adds black magic to what should be
>> a simple process - tag sources, create distro, VOTE on exact bits,
>> push to mirrors - is not an easy sell for some of us.  I consider
>> both the maven release plugin and Nexus in that category.  I guess I
>> may now be forced to use Nexus to publish maven artifacts for o.a.c
>> groupId releases due to no more support for simple replication :-(
>>
>> Phil
>>> Sent from tablet device.  Please excuse typos and brevity.
>>> On Jun 27, 2011 5:53 PM, "Phil Steitz" <phil.ste...@gmail.com> wrote:
>>>> On 6/27/11 2:39 PM, sebb wrote:
>>>>> On 27 June 2011 20:44, Simone Tripodi <simonetrip...@apache.org> wrote:
>>>>>> Hi all guys,
>>>>>> I recently come back focusing on Digester3, fixed some old Issue/added
>>>>>> new minor features and IMHO it is now in a good state to be released.
>>>>>> That's why I'm calling that vote :)
>>>>>> So please cast your votes!!! Many thanks in advance to everybody will
>>>>>> take part to the review, very appreciated!
>>>>>> All the best,
>>>>>> Simo
>>>>>>
>>>>>> Tag:
>>>>>>
>>>>>>
>>> http://svn.apache.org/repos/asf/commons/proper/digester/tags/commons-digester3-3.0/
>>>>>> Site:
>>>>>>
>>>>>> http://people.apache.org/builds/commons/digester/3.0/RC1/site/
>>>>>>
>>>>>> Binaries:
>>>>>>
>>>>>> http://people.apache.org/builds/commons/digester/3.0/RC1/binaries/
>>>>>>
>>>>>> Maven artifacts:
>>>>>>
>>>>>>
>>> http://people.apache.org/builds/commons/digester/3.0/RC1/staged/org/apache/commons/commons-digester3/
>>>>> You don't seem to be using Nexus.
>>>>>
>>>>> Not sure it's possible to release Maven artifacts from folders outside
>>>>> Nexus once a project is looked after by Nexus (all o.a.c components
>>>>> are in Nexus).
>>>> When did that change? I have never used Nexus for [pool] or [dbcp]
>>>> and would prefer not to.
>>>>
>>>> Phil
>>>>> I suggest you ask on the repository@a.o mailing list.
>>>>>
>>>>>> [ ] +1 release it
>>>>>> [ ] +0 go ahead I don't care
>>>>>> [ ] -1 no, do not release it because
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://www.99soft.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
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> 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