[jbosstools-issues] [JBoss JIRA] (JBIDE-10070) Creating OpenShift Express App via JBossTools - "Plugin execution not covered by lifecycle configuration"

[Andre Dietisheim (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638246#comment-12638246 ] 

Andre Dietisheim commented on JBIDE-10070:
------------------------------------------

as far as I understand this warning m2e tells you that m2e will not build the war in it's default build cycle within eclipse. 
To me this error is pointless within eclipse since we just want to know if the project compiles fine within eclipse. The war packaging instruction is used for the build cycle on OpenShift. I dont think that we should configure m2e any different for OpenShift projects.

@Max: WDYT?
                
> Creating OpenShift Express App via JBossTools - "Plugin execution not covered by lifecycle configuration"
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-10070
>                 URL: https://issues.jboss.org/browse/JBIDE-10070
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 3.3.0.M4
>         Environment: RHEL6
> Firefox 3.6.23
> Version: Indigo Release
> Build id: 20110615-0604
> JBoss Tools 3.3.0.M4
> java version "1.6.0_20"
> OpenJDK Runtime Environment (IcedTea6 1.9.10) (rhel-1.40.1.9.10.el6_1-x86_64)
> OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) 
>            Reporter: Len DiMaggio
>            Assignee: Andre Dietisheim
>             Fix For: 3.3.0.Beta1
>
>         Attachments: JBIDE-10070-Screenshot.png
>
>
> The app is created, but this error is reported in Eclipse:
> Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile, phase: compile)
> Line 6 - what's the issue here with the war packaging?
> ------
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>testApp3</groupId>
>   <artifactId>testApp3</artifactId>
>   <packaging>war</packaging>        
>   <version>1.0</version>
>   <name>testApp3</name>
>   <properties>
>     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
>   </properties>
>   <!--<dependencies>
>     <dependency>
>       <groupId>org.jboss.spec</groupId>
>       <artifactId>jboss-javaee-6.0</artifactId>
>       <version>1.0.0.Final</version>
>       <type>pom</type>
>       <scope>provided</scope>
>     </dependency>
>   </dependencies>-->
>   <profiles>
>     <profile>
>      <!-- When built in OpenShift the 'openshift' profile will be used when invoking mvn. -->
>      <!-- Use this profile for any OpenShift specific customization your app will need. -->
>      <!-- By default that is to put the resulting archive into the 'deployments' folder. -->
>      <!-- http://maven.apache.org/guides/mini/guide-building-for-different-environments.html -->
>      <id>openshift</id>
>      <build>
>         <finalName>testApp3</finalName>
>         <plugins>
>           <plugin>
>             <artifactId>maven-war-plugin</artifactId>
>             <version>2.1.1</version>
>             <configuration>
>               <outputDirectory>deployments</outputDirectory>
>               <warName>ROOT</warName>
>             </configuration>
>           </plugin>
>         </plugins>
>       </build>
>     </profile>
>   </profiles>
> </project>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira