Hello J�rg,
Well, fortunately this *is* a feature of Maven. All properties form the master project are inherited in the subproject. This allows uniform settings for all subprojects controlled in one file.
But - as you've detected - this creates some hassle for some plugins working on the main project. You will have to set those properties dynamically using Jelly, if you're running the main project. But be aware, that anything from maven.xml is also inherited!
Well, I admit that this behaviour allows to share properties and goals, and that it could be a good think.
But isn't that the purpose of the <extend> element in the project.xml of each subproject ?
Here is my projects structure :
prototype-dao
prototype-test
... other modules
prototype-webapp
prototype-common ( used with <extend> element by project.xml files of other modules to share common informations on developers list, default projects properties, current development version number, ...)
prototype-multiproject ( used only for piloting other projects's builds, and for aggregating the website of all subprojects, NOT to do some sort of properties inheritence ...)
And what about this use case :
In a subproject, I want to use default values for the properties recognized by a plugin goal. So I don't define those properties, just let them get their defaults from the plugin.
But since the multi-project is bicephal (it is a project on its own, and it serves the purpose of controlling other projects), it may have sete the property to its own use, and the result is that in the subproject, we don't have the default value from the plugin anymore.
I thought the mechanisms of inheritence via <extend> was to avoid duplication in the maven files, but I didn't thought that inheritence was done from the multi-project project too.
--
Laurent
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
