[
https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584449#comment-13584449
]
Marshall Schor commented on UIMA-2560:
--------------------------------------
I suggest we (a) confirm the new design doesn't work for 3.7 Eclipse, and then
(b) figure out why it doesn't work and put in some simple (?) workaround if
possible for that. For instance, if the reason for not working is (as
mentioned above) that embedded JARs in a plugin need to be deployed by
"unpacking" the Jar when it is installed by the installer, there's an Eclipse
directive for that, part of Eclipse 3.7 (Indigo) - Eclipse-BundleShape ::= (
'jar' | 'dir' ) - see
http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fbundle_manifest.html.
> 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
