On 25/05/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
Sure, I was envisaging that it could be fixed in 2.0.7 after which the release plugin could have 2.0.7 as a prerequisite.
I've had a look at the code required to simulate @requiresDependencyResolution, but it will require 2.0.6 due to the changes introduced by MNG-1577. If we have to depend on 2.0.6, does it not make sense to fix the root of the problem in 2.0.7 and depend on that instead? With regard to the proposed solution:
However, there is an alternative: you can combine the reactor projects (which you should have), with the artifacts returned from manual resolution (and using the filtering to omit the projects in the reactor when you perform that).
I'm not sure this will work since the reactor projects would be filtered from the project's dependencies, thus their transitive dependencies would not be resolved. Is the effect we're trying to achieve more akin to putting the reactor project artifacts into the managed dependencies map? Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
