[
https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556444#comment-13556444
]
Marshall Schor commented on UIMA-2560:
--------------------------------------
re: re-adding the dependencies, using copy-dependencies instead of unpack:
This is probably a good thing. I recall noticing at one point that, in
general, it was important to keep each embedded dependency as its own Jar,
because if they were unpacked, then if each one had a LICENSE and NOTICE file,
they would "overlay" one another, losing the individual JAR's information
(except for the last one). It seems that, in general, the OSGi consumption
mechanisms correctly support embedded Jars (within Jars).
re: packaging set to "jar" not "bundle" - the packaging is set to JAR to avoid
having the maven-bundle-plugin build the JARs, because (at the time the POMs
were constructed), the bundle target didn't let you insert the LICENSE and
NOTICE files into the JARs.
> Eclipse m2e complains about unmapped maven plugins
> --------------------------------------------------
>
> Key: UIMA-2560
> URL: https://issues.apache.org/jira/browse/UIMA-2560
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: parent-pom-4
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Fix For: parent-pom-5
>
>
> Recent versions of Eclipse m2e complain about Maven plugins in the UIMA
> master pom not being covered by m2e lifecycle plugins:
> * uima-build-helper-maven-plugin
> * maven-dependency-plugin
> Add m2e metadata to the master POM to handle these.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
