[
https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552785#comment-13552785
]
Marshall Schor commented on UIMA-2560:
--------------------------------------
Another point: I think there's some meta-configuration for m2e which says
whether or not to use projects in the workspace to resolve references, or not.
It's "normally" set to use projects, so as to pick up development level changes
(before JARs are created and "installed" to the .m2 repo). But you can change
that.
Another idea: how about making the unpack-dependencies step conditional on
there being a Jar, and otherwise, just using the folders /target/classes?
> 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
