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).
Long term, we should reintroduce the tag when Maven itself can
properly cope with the projects not being installed.
- Brett
On 22/05/2007, at 2:26 AM, Mark Hobson wrote:
On 01/02/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Edwin - can we double check the requirement here. I recently removed
this to prevent the problem of it failing if you haven't installed
the project first.
I was planning to reintroduce @requiresDependencyResolution test on
release:prepare to generate release poms, since we need the resolved
artifact versions from project.getArtifacts. Would a manual
ArtifactResolver.resolveTransitively be any better that introducing
this annotation, or is there an alternative method of resolving
artifact versions?
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]
