[
https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552782#comment-13552782
]
Marshall Schor commented on UIMA-2560:
--------------------------------------
Sorry to be late to this party :-) but I'm delighted that others are grappling
with these issues!
Some details: IIRC, the builds for the OSGi runtimes was done in a slightly
strange way: the maven-bundle-plugin was used in a mode which only built the
MANIFEST.MF file, but didn't build any JARs. This was because the Jar building
(at the time this was done) didn't do the normal things we do with all of our
JAR building (via some common configuration in the UIMA parent-pom) to insert
License/Notice kinds of things.
Because of this, I think the unpack-dependencies is needed to actually put in
the content into the JAR that is built.
> 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
