2011-12-15 6 views
27

Sto usando STS e ho importato un progetto GWT da un'altra macchina. Il progetto utilizza m2eclipse. Ricevo questi due errori durante la creazione del progetto:Perché ricevo un errore di "esecuzione del plugin non coperto dalla configurazione del ciclo di vita con GWT"?

Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:gwt-maven-plugin:2.2.0:i18n (execution: default, phase: generate-sources) pom.xml /contactsgwt line 175 
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-war-plugin:2.1.1:exploded (execution: default, phase: compile) pom.xml /contactsgwt line 198 

Cosa c'è che non va? C'è qualche ulteriore configurazione da fare in modo che lo gwt maven plugin funzioni?

Il codice pom.xml che causa l'errore:

<!-- GWT Maven Plugin --> 
<plugin> 
    <groupId>org.codehaus.mojo</groupId> 
    <artifactId>gwt-maven-plugin</artifactId> 
    <version>2.2.0</version> 
    <executions> 
     <execution> 
      <goals> 
       <goal>compile</goal> 
       <goal>test</goal> 
       <goal>i18n</goal> 
      </goals> 
     </execution> 
    </executions> 
    <!-- Plugin configuration. There are many available options, see gwt-maven-plugin documentation at codehaus.org --> 
    <configuration> 
     <runTarget>Contacts.html</runTarget> 
     <hostedWebapp>${webappDirectory}</hostedWebapp 
     <i18nMessagesBundle>es.indra.gwt.contactsgwt.client.ContactsMessages</i18nMessagesBundle> 
    </configuration> 
</plugin> 

<!-- Copy static web files before executing gwt:run --> 
<plugin> 
    <groupId>org.apache.maven.plugins</groupId> 
    <artifactId>maven-war-plugin</artifactId> 
    <version>2.1.1</version> 
    <executions> 
     <execution> 
      <phase>compile</phase> 
      <goals> 
       <goal>exploded</goal> 
      </goals> 
     </execution> 
    </executions> 
    <configuration> 
     <webappDirectory>${webappDirectory}</webappDirectory> 
    </configuration> 
</plugin> 

<plugin> 
    <groupId>org.maven.ide.eclipse</groupId> 
    <artifactId>lifecycle-mapping</artifactId> 
    <version>0.9.9-SNAPSHOT</version> 
    <configuration> 
     <mappingId>generic</mappingId> 
     <configurators></configurators> 
     <mojoExecutions> 
      <mojoExecution runOnIncremental="true">org.codehaus.mojo:gwt-maven-plugin:2.2.0:i18n</mojoExecution> 
      <mojoExecution runOnIncremental="true">org.apache.maven.plugins:maven-resources-plugin:2.4.1:resources</mojoExecution> 
      <mojoExecution runOnIncremental="false">org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile</mojoExecution> 
      <mojoExecution runOnIncremental="false">org.apache.maven.plugins:maven-war-plugin:2.1.1:exploded</mojoExecution> 
      <mojoExecution runOnIncremental="false">org.apache.maven.plugins:maven-resources-plugin:2.4.1:testResources</mojoExecution> 
     </mojoExecutions> 
    </configuration> 
</plugin> 
+0

collegate a: http://stackoverflow.com/questions/9142533/plugin-execution-not-covered-by-lifecycle- configuration-jbossas-7-ear-archetype – Gray

risposta

46

Se si utilizza Eclipse Indigo (3.7) si deve attivare il plugin ciclo di vita. Vedere here per ulteriori dettagli.

Basta aggiungere questa sezione pluginManagement alla sezione build del file pom.xml

<pluginManagement> 
    <plugins> 
     <plugin> 
      <groupId>org.eclipse.m2e</groupId> 
      <artifactId>lifecycle-mapping</artifactId> 
      <version>1.0.0</version> 
      <configuration> 
       <lifecycleMappingMetadata> 
        <pluginExecutions> 
         <pluginExecution> 
          <pluginExecutionFilter> 
           <groupId>org.codehaus.mojo</groupId> 
           <artifactId>gwt-maven-plugin</artifactId> 
           <versionRange>[2.4.0,)</versionRange> 
           <goals> 
            <goal>resources</goal> 
            <goal>compile</goal> 
            <goal>i18n</goal> 
            <goal>generateAsync</goal> 
           </goals> 
          </pluginExecutionFilter> 
          <action> 
           <execute /> 
          </action> 
         </pluginExecution> 
         <pluginExecution> 
          <pluginExecutionFilter> 
           <groupId>org.apache.maven.plugins</groupId> 
           <artifactId>maven-war-plugin</artifactId> 
           <versionRange>[2.1.1,)</versionRange> 
           <goals> 
            <goal>exploded</goal> 
           </goals> 
          </pluginExecutionFilter> 
          <action> 
           <execute /> 
          </action> 
         </pluginExecution> 
        </pluginExecutions> 
       </lifecycleMappingMetadata> 
      </configuration> 
     </plugin> 
    </plugins> 
</pluginManagement> 
+0

grazie !! questo ha reso il trucco – Neets

+1

Grazie per la tua risposta. Possiamo aggiungere generateAsync nella prima sezione . Perché un errore simile può verificarsi per l'obiettivo generateAsync e questa aggiunta risolve questo errore. – ovunccetin

+1

@ovunccetin grazie per il suggerimento. Ho aggiornato la risposta –

Problemi correlati