IMO, this is indicative of a need to allow a plugin to call back into
the core and resolve/retrieve the project's dependencies (and it's
not the only case; see any of the IDE plugins). I'm not sure that I'm
actually using a different resolver implementation, though...I don't
remember
On 30 Jul 07, at 12:27 AM 30 Jul 07, John Casey wrote:
I've added code in 2.2-beta-2-snap to address this problem...at
least, it should address it. I added resolution to the plugin
before 2.2-beta-1 because there were issues when people wanted to
create an assembly that didn't require
On Jul 30, 2007, at 8:18 AM, Jason van Zyl wrote:
I've added code in 2.2-beta-2-snap to address this problem...at
least, it should address it. I added resolution to the plugin
before 2.2-beta-1 because there were issues when people wanted to
create an assembly that didn't require
The assembly plugin doesn't seem to obey a hard version that I am
specifying in my POM as [1.2-alpha-9]. In addition I have this in the
dependencyManagement section of Maven's parent POM and it still
ignores it.
Right now I cannot get the assembly plugin to use the hard version I
am
Since John's on holidays you probably won't get a full answer for a
little bit, but I took a quick dig in the svn logs and would guess:
- this was to work around limitations in the artifact resolver
(http://svn.apache.org/viewvc?view=revrevision=438528)
- it delegates to the original artifact
I've added code in 2.2-beta-2-snap to address this problem...at
least, it should address it. I added resolution to the plugin before
2.2-beta-1 because there were issues when people wanted to create an
assembly that didn't require dependencies to be resolved, and the
dependencies couldn't
