On 23/05/2007, at 8:27 PM, Mark Hobson wrote:
On 21/05/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Using the manual resolution would only work if an earlier step in the
release:prepare process had definitely built all the dependencies.
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 think I see what you mean. Do you envisage similar code to
DefaultPluginManager.resolveTransitiveDependencies? Only problem is
that I haven't got access to a MavenSession to obtain the local repo -
is that obtainable any other way?
Yep, there's a few examples of plugins that re-use the resolution
mechanism and though I've never used it maven-downloader is meant to
encapsulate that in an easy to use API as well.
Long term, we should reintroduce the tag when Maven itself can
properly cope with the projects not being installed.
How would @requiresDependencyResolution resolve dependencies if they
weren't in a repo nor the reactor? Or is the reactor not considered
at the moment?
The reactor is not considered at the moment, which is the problem in
this case.
Cheers,
Mark
---------------------------------------------------------------------
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]
