[
https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552324#comment-13552324
]
Richard Eckart de Castilho commented on UIMA-2560:
--------------------------------------------------
Thanks for the pointer to the wiki page.
I am not sure if the below is still true. First, I never made that experience
in the past, e.g. when I was working with OSGi/PDE and wrapped existing
third-party libraries as bundles, I never observed this problem. Second, the
uimaj-core classes from the uimaj-ep-runtime were properly found when I ran the
CAS Editor using "Run as -> Eclipse application". Of course there might be
problems when running the actual JARs built with Maven that did not appear in
my test run due to the m2e-tycho magic.
{quote}
The inline=true flag is set when embedding dependencies, to avoid having the
bundle jar contain within itself, other jars. This flag puts the contents of
the inner jars into the containing jars. This is needed because the OSGi or
Eclipse mechanisms doesn't see exports coming from these jars within jars. See
the statements about "Unzipping JARs" in the Eclipse Help.
{quote}
Btw, I am using Eclipse 4.2.1 (M20120914-1800), m2e 1.2.0.20120903-1050 and the
Tycho Project Configurators 0.6.0.201207302152.
> 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
