Hi, >> > Why not just have 2 parent poms, parent-with-assembly and > parent-without-assembly and let the child pom attach the most > appropriate parent. Yes, this would work. Anyway, I'm inclined to consider this a bug. In my opinion, declaring some configuration property using an empty XML element should effectively undo any value set in a parent configuration.
Given a parent POM with something like
---------- parent ----------
<plugin>
..
<configuration>
<aProperty>value</aProperty>
<someProperties>
<someProperty>anotherValue</someProperty>
</someProperties>
</configuration>
</plugin>
--------------------------------
the following child POM should yield a plugin configuration where
the inherited properties are undefined/not set:
---------- child ----------
<plugin>
..
<configuration>
<aProperty/>
<someProperties/>
</configuration>
</plugin>
--------------------------------
From my experience, 'unsetting' inherited non-collection properties
already works this way (though I'm not really sure if the corresponding
setter method isn't called with a NULL/empty value , as opposed to not
being called at all).
Regards,
Tobias
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
signature.asc
Description: OpenPGP digital signature
