Hi Andrus,
Yes, you're right. Thanks for the tip. I tried this but
maven-wolifecycle-plugin has transitive dependencies that are in
SNAPSHOT version too. So, it's a recursive problem. :(
Cheers,
Henrique
Andrus Adamchik wrote:
> I think release decisions should be made on the grounds of the code
> readiness (on which I can't comment, as I only worked on a small chunk
> the plugin). However IIRC there is a workaround for you to release your
> software with WOProject dependency - instead of "SNAPSHOT", use the
> exact build number as the dependency version in the POM, e.g.
> "2.0-20061207.104927-8" or similar. It worked for me in the past.
>
> Cheers,
> Andrus
>
>
> On Dec 11, 2006, at 4:20 PM, Henrique Prange wrote:
>> Hi Ulrich and Andrus,
>>
>> I'm trying to release a project that depends on
>> maven-wolifecycle-plugin. As this plug-in is in SNAPSHOT version, I
>> can't do the release:prepare successfully on my project. It's
>> necessary to make a release of maven-wolifesycle-plugin first.
>>
>> Does woproject could be released even as an alpha or beta version?
>>
>> Cheers,
>>
>> Henrique
>>
>> --
>> \o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda
>> | Phone: 55-21-2710-0178 E-mail: hprang..oleque.com.br
>> / \ http://www.moleque.com.br
>>
>
>
--\o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda | Phone: 55-21-2710-0178 E-mail: hprang..oleque.com.br / \ http://www.moleque.com.br
This archive was generated by hypermail 2.0.0 : Wed Dec 13 2006 - 12:28:45 EST