merge build tooling artifacts into one, to simplify release process
-------------------------------------------------------------------
Key: UIMA-1914
URL: https://issues.apache.org/jira/browse/UIMA-1914
Project: UIMA
Issue Type: Improvement
Components: Build, Packaging and Test
Reporter: Marshall Schor
Assignee: Marshall Schor
When build artifacts are updated, releasing can be difficult. This is because
some of the artifacts are dependent on the top parent pom being built, and
those artifacts, in turn, depend on the top parent pom (circular refs). Based
on discussion on the mailing list (see
http://uima.markmail.org/thread/ryh6voctne6vqb7d ), it would simplify things to
collapse all of the build artifacts into just one parent-pom.
Do this, making the packaging of that a Jar, and putting into it also the
resource bundles needed by the other parent poms. Change the resource bundle
need for assemblies to just plain descriptor references, eliminating the need
for bundle refs. Do what's needed to override the normal source-release
assembly, so that our "improved" version is used (it works with
flat-hierarchies).
Merge all the other parent-poms into one, using either the existence of some
file/directory (e.g. src/docbook ) to trigger the particular profile, or, where
none can be found, make a new trigger consisting of a file at the top level
called something like:
"marker-file-identifying-xxxxxx". Those projects which need these profiles
will need to have (empty) files like this to trigger the profile.
Use this mechanism instead of pointing to different parent-poms to control the
build (as there will now be just one parent pom for all uima projects).
Update the projects to use the new parent pom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
