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 suggetions? Regards, James Masanz > -----Original Message----- > From: [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. ;-)
