To solve a bunch of nagging issues, and at the suggestions of several on this
list (thank you!), I've now completed merging all of the parent poms into just
one.
The previous method where a project selected which kind of build to have, by
selecting a particular parent is replaced by activating one or more particular
"profiles" in the parent-pom.
Some of these profiles are activated by the presence of standard files, such as
docbook source file directory under src/main activating the docbook processing.
Others are activated by the project having a 0 length specially named file
"marker-file-identifying-xxxx".
Others (the inclusion of the ibm-notice variant) is triggered by adding the
property:
<postNoticeText>${ibmNoticeText}</postNoticeText>
I think this results in a cleaner, more maintainable and releasable approach.
I've checked in the new top level pom (called parent-pom) and one other file
holding *all* the resources needed for the build in a Jar file.
I've updated the uimaj, uima-as, and add-ons to reference the new parent-pom,
and ran mvn install on everything and spot-checked the results. It's possible
I've overlooked something, so please post here or open Jira issues if you spot
something that's not working :-).
-Marshall
