Hi,
Some opinions needed. Currently we have a problem in: MNG-895 (cannot
add resources to a profile).
Basically, profiles operate identically to inheritence, and so resources
are not merged through inheritence, but if they do exist in the parent
they are inherited (eg src/main/resources from the super POM).
So, this seems a bit inconsistent to me. If you have 0 resources you get
the parent, if you have 1 you don't. But if you enable merging you have
no way to turn off inherited resources like src/main/resources.
To me, I don't see why resources should be inherited at all except to
apply that default, especially since ${basedir}/my-resources in the
parent actually doesn't point to teh parent's basedir but the
subprojects basedir. Furthermore, with aggregation, its possible that
new resource roots would be introduced for the parent and not the children.
Options:
1. handle profiles differently (merge resources, but don't merge for
inheritence)
2. merge for inheritence and profiles (we can probably live with it
because the extra directories will just be ignored in the children)
3. keep as is (inherit resources element if there is none in the
subproject, but don't merge, profiles would need to redefine resources)
4. turn off inheritence of resources altogether (src/main/resources
would be applied as a default after the fact if the end result is empty).
Thoughts?
For me:
1. -1
2. +0
3. +1
4. -0
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
