|
My project layout is as follows: common-build The extensions of the kernel are developed independently and can thus not be stored under kernel-module. Each module has a project.xml which says: For me this is not a minor bug, but a show stopper. Bug's priority should be set to critical as it is in the duplicated bug #1513. major is fairer. We tend to drive priority by "fix for" version. A workaround is passing the property in the command line, e.g. This way it's available to subprojects From Dr Wes Munsil: maven.property.inheritance=true The workaround suggested by Wes Munsil does not work for me. I tried to set "maven.property.inheritance=true" at the following places
looking at the code made this fairly obvious what was going wrong. I have it fixed, and will commit this evening. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
this is a regression resulting from fixing >1 level of inheritence. It only fails for build in properties (most importantly, maven.repo.remote).