Hi,
We have a problem with ${basedir} evaluation under M$ Windows which
gives us a path mixing \ and / when filtering resources.
This seems to be coming from plexus-utils (cf.
http://jira.codehaus.org/browse/MRESOURCES-10) and looks corrected since
plexus-utils 1.2 :o)
So I have tried to upgrade maven-resources-plugin dependecy to
plexus-utils 1.4 (this comes from maven-resources-plugin depending on
maven-compiler-plugin depending on plexus-utils:1.0.4) but this did not
correct my problem.
Emmanuel Venisse suggested to upgrade the plexus-utils.jar in
$M2_HOME/core but this did not correct our problem:o( and raised a
question in my mind:
Who is in charge with interpreting ${basedir} ? Is it the plexus /
plexus utils from maven's core or the plexus-utils which is referenced
in transitive dependency from the plugin ?
I am quite at lost here because while I understand that plugins depend
on the maven-plugin-api and maven-compiler-plugin and etc. this should
be a 'provided' dependency as you need them to compile but they should
be provided by the maven/plexus container. This way, the plugins may not
be backward compatible but upgrading plexus into maven should be far easier.
My 2 cents
Emmanuel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
