The uninstall of the old m2e plugins corrupted my old Eclipse IDE installation. So, I started from scratch (download of Eclipse IDE 4.2.1 Juno), new workspace, fresh check out of trunk, (bind my JDK to the maven builder instead of JRE), maven > update project configuration , refresh. I can confirm that the new plugin works as expected so far...
Note: There were still some references to nonexistent directories src/test/java which should get cleaned up. --Pei > -----Original Message----- > From: Masanz, James J. [mailto:[email protected]] > Sent: Tuesday, October 23, 2012 1:44 PM > To: '[email protected]' > Subject: RE: latest build instructions > > So my updated list of steps I needed, since I was using a downlevel version of > m2e: > > - download patch from issue CTAKES-65 > - execute 'svn patch ctakes-jcasgen-maven-plugin.diff' > - refresh eclipse workspace > - use context menu option Maven->Update Project Configuration > - uninstall maven (m2e 1.0) and supporting plugins (Maven SCM Handler for > Subversive 0.13 etc) > - install m2e 1.2 > > Now with Build Automatically I am seeing that if I change a non type system > file, type systems are not regen'd. > And if I change a type system file, the type system classes are regenerated > and then compiled. > > Note, I uninstalled m2e 1.0 because Help->Check for updates was giving me > errors about Cannot complete the install because of a conflicting > dependency. Only one of the following can be installed at once: > > (full details of the errors are after my signature) > > Thanks for the help. > > Regards, > James Masanz > > Cannot complete the install because of a conflicting dependency. > Software being installed: m2e connector for build-helper-maven-plugin > 0.15.0.201109282249 (org.sonatype.m2e.buildhelper.feature.feature.group > 0.15.0.201109282249) > Software currently installed: Maven SCM Handler for Subversive > 0.13.0.201106211115 (org.sonatype.m2e.subversive.feature.feature.group > 0.13.0.201106211115) > Only one of the following can be installed at once: > Maven Integration for Eclipse 1.0.0.20110607-2117 (org.eclipse.m2e.core > 1.0.0.20110607-2117) > Maven Integration for Eclipse 1.0.200.20111228-1245 (org.eclipse.m2e.core > 1.0.200.20111228-1245) > Maven Integration for Eclipse 1.2.0.20120903-1050 (org.eclipse.m2e.core > 1.2.0.20120903-1050) > Maven Integration for Eclipse 1.1.0.20120530-0009 (org.eclipse.m2e.core > 1.1.0.20120530-0009) > Maven Integration for Eclipse 1.0.100.20110804-1717 (org.eclipse.m2e.core > 1.0.100.20110804-1717) > Cannot satisfy dependency: > From: m2e connector for build-helper-maven-plugin 0.15.0.201109282249 > (org.sonatype.m2e.buildhelper 0.15.0.201109282249) > To: bundle org.eclipse.m2e.core [1.1.0,1.2.0) > Cannot satisfy dependency: > From: m2e connector for build-helper-maven-plugin 0.15.0.201109282249 > (org.sonatype.m2e.buildhelper.feature.feature.group 0.15.0.201109282249) > To: org.sonatype.m2e.buildhelper [0.15.0.201109282249] > Cannot satisfy dependency: > From: Maven SCM Handler for Subversive 0.13.0.201106211115 > (org.sonatype.m2e.subversive 0.13.0.201106211115) > To: bundle org.eclipse.m2e.core [1.0.0,1.1.0) > Cannot satisfy dependency: > From: Maven SCM Handler for Subversive 0.13.0.201106211115 > (org.sonatype.m2e.subversive.feature.feature.group 0.13.0.201106211115) > To: org.sonatype.m2e.subversive [0.13.0.201106211115] > > > > -----Original Message----- > > From: ctakes-dev-return-669- > [email protected] > > [mailto:ctakes-dev-return-669- > > [email protected]] On Behalf Of Steven > > Bethard > > Sent: Tuesday, October 23, 2012 11:41 AM > > To: [email protected] > > Subject: Re: latest build instructions > > > > On Oct 23, 2012, at 10:21 AM, "Masanz, James J." > > <[email protected]> > > wrote: > > > I did these things: > > > - download patch from issue CTAKES-65 > > > - svn patch ctakes-jcasgen-maven-plugin.diff > > > - refresh eclipse workspace > > > - use context menu option Maven->Update Project Configuration > > > > > > And I now have 8 errors similar to this shown in my Problems view: > > > > > > Plugin execution not covered by lifecycle configuration: > > org.cleartk:jcasgen-maven-plugin:0.9.3:generate (execution: default, > > phase: process-resources) pom.xml /ctakes-assertion line > 27 > > Maven Project Build Lifecycle Mapping Problem > > > > > > I am still a maven newbie, so I may have missed something obvious. > > > Any > > suggestions? > > > > What version of the m2e plugin do you have? You could get this error > > if you were using m2e < 1.1.0. (The current version is 1.2.0.) > > > > If you have a current version of m2e, you can check that the jcasgen- > > maven-plugin you have has the necessary "lifecycle-mapping- > > metadata.xml": > > > > $ unzip -l ~/.m2/repository/org/cleartk/jcasgen-maven- > > plugin/0.9.3/jcasgen-maven-plugin-0.9.3.jar > > Archive: /Users/bethard/.m2/repository/org/cleartk/jcasgen-maven- > > plugin/0.9.3/jcasgen-maven-plugin-0.9.3.jar > > Length Date Time Name > > -------- ---- ---- ---- > > 0 10-20-12 14:08 META-INF/ > > 132 10-20-12 14:08 META-INF/MANIFEST.MF > > 0 10-20-12 14:08 META-INF/m2e/ > > 0 10-20-12 14:08 META-INF/maven/ > > 0 10-20-12 14:08 META-INF/maven/org.cleartk/ > > 0 10-20-12 14:08 META-INF/maven/org.cleartk/jcasgen-maven- > > plugin/ > > 0 10-20-12 14:08 org/ > > 0 10-20-12 14:08 org/cleartk/ > > 0 10-20-12 14:08 org/cleartk/plugin/ > > 445 10-20-12 14:08 META-INF/m2e/lifecycle-mapping-metadata.xml > > 1518 10-20-12 14:08 META-INF/maven/org.cleartk/jcasgen-maven- > > plugin/plugin-help.xml > > 8325 10-20-12 14:08 META-INF/maven/plugin.xml > > 1688 10-20-12 14:08 > > org/cleartk/plugin/JCasGenMojo$JCasGenErrors.class > > 618 10-20-12 14:08 > > org/cleartk/plugin/JCasGenMojo$JCasGenException.class > > 1366 10-20-12 14:08 > > org/cleartk/plugin/JCasGenMojo$JCasGenProgressMonitor.class > > 8460 10-20-12 14:08 org/cleartk/plugin/JCasGenMojo.class > > 6162 10-20-12 14:08 META-INF/maven/org.cleartk/jcasgen-maven- > > plugin/pom.xml > > 116 10-20-12 14:08 META-INF/maven/org.cleartk/jcasgen-maven- > > plugin/pom.properties > > -------- ------- > > 28830 18 files > > > > Steve > > > > > > > > > > > Regards, > > > James Masanz > > > > > >> -----Original Message----- > > >> From: > > >> ctakes-dev-return-661- > [email protected] > > >> [mailto:ctakes-dev-return-661- > > >> [email protected]] On Behalf Of Steven > > >> Bethard > > >> Sent: Saturday, October 20, 2012 7:52 PM > > >> To: [email protected] > > >> Subject: Re: latest build instructions > > >> > > >> On Oct 19, 2012, at 12:29 PM, "Chen, Pei" > > >> <[email protected]> wrote: > > >>> It seems like this issue is affected enough developers... > > >>> My vote would be to add the custom connector by default in the > > >>> various > > >> pom.xml's as Tim/Steve suggested. > > >> > > >> I've just updated the JCasGen Maven plugin and the cTAKES patch to > > >> use an approach that gets rid of the need for installing an m2e > > >> connector in Eclipse. So it should be a pretty obvious win now to > > >> switch from JCasGenPomFriendly + exec-maven-plugin + > > >> build-helper-maven-plugin to the jcasgen-maven-plugin. > > >> > > >> Please try out the patch as described here: > > >> > > >> https://issues.apache.org/jira/browse/CTAKES-65#comment-13480863 > > >> > > >> Steve > > >> > > >> P.S. I think the UIMA folks are going to try to incorporate the > > >> jcasgen- maven-plugin in their next release: > > >> > > >> https://issues.apache.org/jira/browse/UIMA-2471 > > >> http://permalink.gmane.org/gmane.comp.apache.uima.general/4368 > > >> > > >> So we'd be jumping on the right bandwagon. ;-) > > >
