IIRC, path resolution was taking place in the project builder...which
would mean that it could have happened during kenney's cleanup of the
interpolation. Not sure, though. (I'm fairly certain on the timing of
the path translation, though...I'm pretty sure it happened during
project-buildin
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 b
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=rev&revision=438528)
- it delegates to the original artifact
Hi,
I have a question regarding MOJO-866. Hopefully, someone can help me.
In this bug report, someone is invoking the rat:rat goal from the
command line. The plugin fails with a NullPointerException, because
getProject() returns null.
- Are reports supposed to be working, if you are invoking the
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 speci
I will be out of the office starting 18-07-2007 and will not return until
01-08-2007.
I will respond to your message when I return.
Pls. forward all messages to [EMAIL PROTECTED]
I'm trying to find the source of the problem, but it0088 is broken on
trunk and that's the very nasty ${project.build.directory} not
resolving to a full path which caused a tremendous amount of grief
between the 2.0. and 2.0.1 releases.
I can tell immediately what broke it, but if anyone wa
