I've listed the problems in the JIRA entry and started a new thread for this discussion.
The problem is that the ProjectTools end up invoking another maven with mangled information and that this causes target/classes to have a junk plugin.xml which is then used in the jar phase. On 12/21/06, John Casey <[EMAIL PROTECTED]> wrote:
are you sure it wasn't just a case of the IT-staging process somehow hitting the deploy phase of the build? That would've done it. The ITs currently use the maven-invoker, which forks an entirely new Maven process, both for building the test version of the plugin, and for running each test build. So memory pollution isn't really an option. I suppose it's possible that it's picking up the wrong jar from /target, but the deployment process discards that filename anyway... I'll mod the code to delete that plugin jar from the target dir when it's finished... -john On 12/20/06, Barrie Treloar <[EMAIL PROTECTED]> wrote: > > > not sure what went wrong, but look at these: > > http://www.nabble.com/Maven-eclipse-plugin-error-tf2692962.html#a7509615 > > http://jira.codehaus.org/browse/MECLIPSE-192 > > I'm still investigating why this occurs. > > I think it is either the stuff in maven-plugin-testing-tools is > mangling something it shouldn't or jar:jar is picking up the wrong > information from somewhere. > > I'm still trying to work out where the code is for writing > META-INF/maven/plugin.xml which should help resolve why the version is > incorrectly set to test. > > --------------------------------------------------------------------- > 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]
