Hi, > Note how this is a module of the root project and therefore it'd be > redundant to have to re-specify all of the information such as the > contributors, SCM location [0], etc. I only provide the information > that's specific to that module such as the OSGi manifest, > dependencies, etc.
If what you want is to ensure the property is simply non-empty, or matching a particular regex, then take a look at the requireProperty enforcer rule [1]. Or if your goal is to make sure that a property value _differs_ from the value defined in an ancestor, the requirePropertyDiverges rule [2] might be for you. In my case, I really wanted to make sure that all those properties were (re)defined in the child POM, because otherwise, it was too easy for downstream developers to accidentally forget to override things propertly. E.g., the parent POM defines <issueManagement> as the issue tracker for that parent POM itself—but this should never be inherited by the child; instead, every child should define its own <issueManagement> for its own issue tracker. (If you don't have an issue tracker, you can write <issueManagement><system>None</system></issueManagement> to satisfy the enforcer.) Regards, Curtis [1] https://maven.apache.org/enforcer/enforcer-rules/requireProperty.html [2] http://www.mojohaus.org/extra-enforcer-rules/ requirePropertyDiverges.html -- Curtis Rueden LOCI software architect - https://loci.wisc.edu/software ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden Did you know ImageJ has a forum? http://forum.imagej.net/ On Wed, Mar 1, 2017 at 2:17 PM, <org.apache.maven.u...@io7m.com> wrote: > On 2017-03-01T12:46:45 -0600 > Curtis Rueden <ctrue...@wisc.edu> wrote: > > > > In this way, I ensure that all projects which extend our parent add all > the > > useful metadata and properties needed for successful builditude. > > > > Hm, slight issue with this. > > If you take a look at how my projects are usually designed: > > https://github.com/io7m/jtensors/blob/develop/pom.xml > > That's the root pom for the project. It defines all of the project's > information such as plugin versions, dependency versions, metadata such > as the SCM location, site, etc. > > Then, each module looks like this: > > https://github.com/io7m/jtensors/blob/develop/io7m-jtensors-core/pom.xml > > Note how this is a module of the root project and therefore it'd be > redundant to have to re-specify all of the information such as the > contributors, SCM location [0], etc. I only provide the information > that's specific to that module such as the OSGi manifest, dependencies, > etc. > > Using the scijava-maven-plugin RequireElements rule would seem to > require me to specify all of this information again in each module. > Is there a way to avoid this? > > M > > [0] Although I do actually have to re-specify the SCM location due to > an utterly ancient bug/design flaw in the site plugin. >
