'Ello.

On 2017-03-02T08:16:43 -0600
Curtis Rueden <[email protected]> wrote:

> Hi,
> 
> > I do actually want to enforce this, the issue is that I only want to
> > enforce it as far as the first ancestor.  
> 
> Sorry if you stated otherwise in your writeup, but my understanding is that
> you want to define some empty properties in your new root POM, and then
> ensure they are _not_ empty in the next level down. Right?

Yes, but additionally some XML elements as well.

I'd like to enforce that:

  1. Some properties that are defined as empty in the root POM are
     non-empty in all descendants.

  2. Some XML elements that are defined in the root POM (such as
     issueManagement) are overridden _at least once_ between the root
     and any leaf project.

The requireProperty rule you provided does seem to properly handle point
1, but I think that the options we've discussed are too heavy-handed
for point 2. Unless I've missed something obvious, it seems that I can
only require that the XML elements be overridden in *all* descendant
POMs, and this introduces too much redundancy.

M

Attachment: pgpx1cabVCYFf.pgp
Description: OpenPGP digital signature

Reply via email to