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: [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. ;-)
> 

Reply via email to