Pear builder maven plugin should use "Package" mode of buildComponentClassPath
-------------------------------------------------------------------------------
Key: UIMA-1678
URL: https://issues.apache.org/jira/browse/UIMA-1678
Project: UIMA
Issue Type: Bug
Components: Build, Packaging and Test
Reporter: Marshall Schor
Assignee: Marshall Schor
Fix For: 2.3
The part of the PEAR system which sets up the class path (implemented in
buildComponentClassPath method) can be run in two modes, one for "packaging"
and the other for use at "runtime". The difference is that the "runtime" just
uses the specified classpath, while the "packaging" creates a classpath adding
jars found in the lib/ directory.
The Maven plugin to create a package should use the "packaging" version. This
will help with backwards compatibility.
While changing things, the Maven plugin should use a definite order for
building the classpath, starting with the actual artifact, any entries in a
user-specified classpath, and then the jars from the lib directory, last (in
arbitrary order). And it should not add things to the classpath that are
already there (remove duplicates).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
