Hi, On 30/09/16 15:20, [email protected] wrote:
Hi all,we discovered a problem with properties defined in a pom.xml. Properties could be defined in a pom.xml like: <properties> <myProp>default</myProp> </properties> In a maven plugin we fetch all the properties by calling: Properties projectProps = project.getProperties(); Running all this with maven 2 we were able to modify the value of "myProp" within the plugin by: projectProps.put("myProp", "newValue"); So after the execution of the plugin, the property <myProp> has the value "newValue". Running all this with maven 3 that does not work anymore.
First I would say this is by design wrong, cause if you define a property in the pom file I would like to be sure that it will be kept the value I have given and if a plugin (which could it be) will change that I will be really astonished.
Apart from that my question: Why do you need to change existing properties and why not changing the in the pom which is more clearer than mysteriously chaning a property by a plugin?...
Can you give more details about your use case ? Best would be having a real workign example and what kind of problems you are trying to solve with this approach?
Kind regards Karl Heinz Marbaise --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
