The interpolator was only working based on an incorrect assumption for a limited set of expressions. This assumption is
guaranteed by the solution in the interim, until it can be properly reconsidered. The proper solution would be to not
cache an interpolated model, and to apply path translation and then interpolation after retrieving the cached model. However,
this will require some other related changes and should be planned for 2.1.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@390098 13f79535-47bb-0310-9956-ffa450edef68
new interpolator so the one from 2.0 was used and some envar handling was back ported. Unit tests
have been added for envar handling as well as an IT. The maven-core-it script will now set
an envar which is used in it0090.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@368108 13f79535-47bb-0310-9956-ffa450edef68
Now someone might have some more insight here because this failure didn't crop up until yesterday.
About 3 months ago maven-archiver was changed so that the client was responsible for setting
the archiver implementation using:
archiver.setArchiver( new JarArchiver() );
But this code is something that I just added to the PackagingMojo.java file. Using -X says that
version 2.0 of maven-archiver is being used so I'm not exactly sure what is going on here. An
older version of maven-archiver set up its archiver internally so I suppose it might be possible
that something older then 2.0 was being used but this IT should have broken long ago looking
at the code in the PackagingMojo.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@367632 13f79535-47bb-0310-9956-ffa450edef68
Brett Leslie Porter
Jason van Zyl
John Dennis Casey