Are we talking about the same thing? Do you also have a module with a
dependency on your OWN maven plugin located in another module that is part of
the same release?
On 19.11.2009, at 14:00, Martin Schayna wrote:
> We have same scenario. Release plugin only warns "can't change version" on
> dependent projects. Released deliveries are OK.
> Martin Schayna
>
> Peter Niederwieser wrote:
>> In my multi-module project, I have a Maven plugin A and a module B that uses
>> version ${project.version} of A (all modules have the same version number).
>> release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails
>> while processing B because it cannot find version 0.3 of A. Any ideas how to
>> solve this problem?
>> Cheers, Peter
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
