[
https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628599#comment-13628599
]
Marshall Schor commented on UIMA-2560:
--------------------------------------
To get this to work with Eclipse 3.7.2 (a fresh install), the key was to
**not** install m2e from the 3.7.2 Indigo update site (Indigo -
http://download.eclipse.org/releases/indigo ) because that installs a "buggy"
version of m2e, which I could not get to work. I had tried that first, because
that's the "standard" place to go for addon components for the 3.7 release, and
there's an m2e there among many others.
Rather, install m2e from the m2e site: http://eclipse.org/m2e/download/ - I
picked the "latest m2e release (recommended)" and that worked quite well.
For the record, this is version: 1.3.1.20130219-1424 My guess: posted February
19th
The only other plugin I initially installed into my freshly unzipped 3.7.2 was
the Subclipse one. I checked out the UIMA-2560 versions of build and uimaj
from the branches, and did a file->import Existing Maven projects. (well, not
quite true - I had already fooled around with some editing of the base version
- for instance, making the parent pom of the other projects (besides
parent-pom) in the build directory point to the 5-SNAPSHOT version of the build
parent-pom, so they could inherit the m2e settings.)
When doing the import, I got some unresolved m2e connector dialogs. These I
let m2e search for connectors, and it found and installed various ones,
including Tycho. (The "buggy" version of m2e failed when it tried to do this).
There was only one it didn't find a connector for - the remote-resources plugin.
So for that I let it build, and then right clicked one of the errors in the
Problems view that said (I don't remember the exact words) something about
missing an m2e action, and did the "quick fix" pick in the menu. First I tried
to have it discover m2e connectors. For the one it couldn't discover, I told
it to update the pom (in my case, the common uima-wide parent pom in "build")
to ignore this particular plugin (this is the one which copies boilerplate
things into our Jars - standard licenses and notices). We don't need that
action for Eclipse builds - and it will still be done for maven builds done
outside of Eclipse.
Peter - if you have a chance, it would be good if you could try this particular
version of the m2e plugin in a *fresh* unzip of 3.7.2, to see if it just starts
working for you ( fingers crossed :-) )
> 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
