Grhh. My bad. It's now fixed. I have make mavenHome to use for it tests more configurable: * -DmavenHomeUsed= path to a maven 2.x home * or -Pmaven-2.2.1 this profile will download a maven 2.2.1 distrib and use it for integration tests. I will add a jenkins job to run with -Pmaven-2.2.1.
I will start the release process for a 2.12.2 version now. 2012/8/3 Kristian Rosenvold <kristian.rosenv...@gmail.com>: > We just had https://jira.codehaus.org/browse/SUREFIRE-896, and for > some reason the > > /** > * Map of project artifacts. > * > * @parameter expression="${project.artifactMap}" > * @required > * @readonly > */ > private Map<String, Artifact> projectArtifactMap; > > that was converted to : > > > /** > * Map of plugin artifacts. > */ > @Parameter( defaultValue = "${plugin.artifactMap}", required = > true, readonly = true ) > protected Map<String, Artifact> pluginArtifactMap; > > > Does not get injected when running under 2.2.1, which effectively > makes 2.12.1 useless for all 2.2.1 users. > > I have not investigated further into the cause of this, but I think > all release managers need to take special care to run IT's with maven > 2.2.1 as well before releasing newly converted components. > > Kristian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
