Hi Alexander, On Tuesday, 6. February 2024, 02:39:09 CET Alexander Kriegisch wrote: > Jörg, > > I asked for a working example and not theory for a reason: The plugin > POM already uses properties, and it simply does not work to override > them.
Since you seem to use a 3rd party parent, is it public? Then you could tell us which one... [snip example] > Overriding the property in the project using the plugin does not seem to > have any effect. I verified that the plugin POM still contains the > property and the version number is not flattened in any way. > > Is this even supposed to work like that? Are plugin properties > overridable like this? It would be nice, but I guess they are not part > of the reactor. That is also the reason why my project can use one > version of a dependency and a plugin can use another one without them > affecting each other. This failed for me only, when I tried to make the version of a Maven extension configurable. > So please, if you have a working example for what you say should work, > please provide it, so I can reproducer what you recommend me to do. Give me a head start by pointing me to the parent pom. Regards, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
