[
https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552871#comment-13552871
]
Richard Eckart de Castilho commented on UIMA-2560:
--------------------------------------------------
* re jar building: maybe there is another approach to JAR building that doesn't
need unpack-dependencies and that can be run in a profile so that it is not
enabled when run within Eclipse. For example an ant-run post-processing step.
* re m2e disable workspace resolution: it is possible to disable that, per
project even. I find workspace resolution very useful though. It will probably
also be confusing and lead to unexpected effects if resolution is disabled for
some projects but not for others. -1 on this one.
* re conditional unpack-dependencies: +1 for conditional. Instead of testing
for a JAR (no idea how that could be done), I suggest to test for Eclipse/m2e.
There are special properties that are set during an m2e build which can be use
to enable/disable profiles.
> 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
