[
https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629162#comment-13629162
]
Marshall Schor commented on UIMA-2560:
--------------------------------------
With this approach, you get a "mixed" system - the plugins that are built using
the technique of copying JARs into one Jar need to be replace in the dropins
folder, but other plugins, written as more "normal" eclipse ones, don't need
this special treatment. But, I see your "engine" plugin depends on and
includes the "core".
So, you are correct; this isn't a good workaround. Let's think of a better one
:-)
The ideal would not need any JARs to be built, for the plugins that are in the
workspace / under development.
There would be 2 different builds: one for development, running off of class
folders (no Jars), and the other for releases and builds outside of Eclipse.
The latter would operate as it does now.
I wonder if Tycho has some special ability to do good things here?
> 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
