The behaviour is "intended". I am not sure if there is any reactor-wide map that is available anywhere.
Kristian 2015-03-11 17:10 GMT+01:00 Karl Heinz Marbaise <[email protected]>: > Hi, > > currently i have the problem creating a plugin which adds some > properties...to the current project... > > @Parameter(defaultValue = "${project}", readonly = true, required > = true) > private MavenProject mavenProject; > > > mavenProject.getProperties().put("NAme", "Value"); > > > This results in having the new property only in the current project (root > of my multi module build) but thos properties aren't being available in > other project deeper in the module levels...This > seemed to be the result of optimizing it to execute only in > executionRoot()... > > So after further investigation i have found that for example the > buildnumber-maven-plugin explicit goes through the list of reactor projects > and adds the property explicit to each of the reactor modules... > > > Is this intended behaviour or am i doing something wrong or is there a > more elegant way to solve this? > > Kind regards > Karl Heinz Marbaise > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
