On 8/5/2011 9:06 PM, Richard Eckart de Castilho wrote: > I am still trying to get an UIMA workspace set up in Eclipse with m2eclipse > and still fail - mostly. I feel a bit odd here about why it's so non-trivial > to get a proper Eclipse workspace for UIMA with m2eclipse. Probably I'm just > plain stubborn because I believe that I should not have to run external tools > (like mvn eclipse:eclipse or even clean install) when developing software in > an IDE... I mean it should be an "integrated development environment", right?
Right. Something very strange is happening. See my earlier post. I started with a brand new, freshly unzipped version of Eclipse 3.6.2, installed just 2 plugins (Subversion and m2Eclipse), and then got things going by 1) checking out of SVN (using a svn command line client, using the command: svn checkout http://svn.apache.org/repos/asf/uima/uimaj/trunk myLocalWorkingDirectory 2) in Eclipse, using File -> Import -> Maven -> Existing Maven projects, and imported things. > > Anyway... > > One problem seems to be the uimaj-ep-runtime module. It uses a > "unpack-depencendies" goal which throws an error in Eclipse 3.6.2 and which > is completely unsupported in Eclipse 3.7 (m2e). > > I finally managed to "run" the uima-ep-cas-editor" module from Eclispe (3.7), > but only after I had turned uimaj-core itself into an Eclipse plugin project > by adding the "marker-file-identifying-eclipse-plugin", adding a > "plugin.xml", and adding a minimal maven-bundle-plugin configuration in the > POM. > > I wonder, is there a special reason to unpack and re-package the core UIMA > JARs into a single "UIMA Runtime" plugin? Since OSGi bundles are just like > regular jars plus a bit of meta-data, how about not having uimaj-ep-runtime > and add the OSGi metadata directly to uimaj-core and friends? > > I also did disable the uima-helper-maven-plugin because it produced error > markers all over the place with m2e(lipse) from Eclipse 3.7. > > Also m2e produces a number of Maven-related warnings about managed dependency > versions being overridden in modules and superfluous groupIds and versions. Some of these may be issues with 3.7 - I haven't tried that yet. -Marshall > > Cheers, > > Richard >
