[ https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556338#comment-13556338 ]
Richard Eckart de Castilho commented on UIMA-2560: -------------------------------------------------- I also created a branch of the "build" module which contains the master parent-pom. Right about the JAR. The MANIFEST.MF seems correct though, just the JARs are missing. I re-added the dependencies plugin, but this time using copy-dependencies instead of unpack dependencies. On the command line build, that seems to create a proper JAR. In Eclipse, the copy-dependencies goal is ignored and the tycho plugin should take care of configuring the classpath properly when "Run As -> Eclipse Application" is used. I googled a little and it appears that the JARs are not may not be copied the maven-bundle-plugin because the packaging is set to "jar" not "bundle" - but just changing the packging didn't work either in a quick test. > 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