[JBoss JIRA] (JBIDE-10070) Creating OpenShift Express App via JBossTools - "Plugin execution not covered by lifecycle configuration"
2:36 p.m.
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
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-environm... -->
<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
2:38 p.m.
[
https://issues.jboss.org/browse/JBIDE-10070?page=com.atlassian.jira.plugi...
]
Len DiMaggio commented on JBIDE-10070:
--------------------------------------
./eclipse
Oct 27, 2011 2:54:30 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.0.Beta2
Oct 27, 2011 2:54:30 PM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.0.Beta3
Oct 27, 2011 2:54:30 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.0.Beta3
Oct 27, 2011 2:54:46 PM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM00200: Remote connection failed: java.io.IOException: Message data for
non-existent channel
15:05:39.348 [Worker-15] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh
request: []
15:05:39.926 [Worker-15] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing:
[/testApp3/pom.xml]
15:05:40.064 [Worker-15] DEBUG o.e.m.c.internal.embedder.MavenImpl - Reading Maven
project: /home/ldimaggi/git/testApp3/pom.xml
15:05:40.172 [Worker-15] DEBUG o.e.m.c.internal.embedder.MavenImpl - Read Maven project:
/home/ldimaggi/git/testApp3/pom.xml in 108 ms
15:05:40.172 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IEditorMarkerService
15:05:40.186 [Worker-15] DEBUG o.e.m.c.i.l.LifecycleMappingFactory - Loading lifecycle
mapping for MavenProject: testApp3:testApp3:1.0 @ /home/ldimaggi/git/testApp3/pom.xml.
15:05:40.194 [Worker-15] INFO o.e.m.c.i.l.LifecycleMappingFactory - Using DEFAULT
lifecycle mapping for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml.
15:05:40.194 [Worker-15] DEBUG o.e.m.c.i.l.LifecycleMappingFactory - Loaded lifecycle
mapping in 9 ms for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml.
15:05:40.197 [Worker-15] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources (execution:
default-resources, phase: process-resources)' on resource
'/testApp3/pom.xml'.
15:05:40.198 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:40.198 [Worker-15] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile,
phase: compile)' on resource '/testApp3/pom.xml'.
15:05:40.199 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:40.199 [Worker-15] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-resources-plugin:2.4.3:testResources (execution:
default-testResources, phase: process-test-resources)' on resource
'/testApp3/pom.xml'.
15:05:40.199 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:40.199 [Worker-15] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (execution:
default-testCompile, phase: test-compile)' on resource '/testApp3/pom.xml'.
15:05:40.200 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:40.201 [Worker-15] DEBUG o.e.m.c.i.p.r.DefaultMavenDependencyResolver - Resolving
dependencies for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml
15:05:40.201 [Worker-15] DEBUG o.e.m.c.internal.embedder.MavenImpl - Reading Maven
project: /home/ldimaggi/git/testApp3/pom.xml
15:05:40.209 [Worker-15] DEBUG o.e.m.c.internal.embedder.MavenImpl - Read Maven project:
/home/ldimaggi/git/testApp3/pom.xml in 7 ms
15:05:40.209 [Worker-15] DEBUG o.e.m.c.i.p.r.DefaultMavenDependencyResolver - Resolved
dependencies for MavenProject: testApp3:testApp3:1.0 @ /home/ldimaggi/git/testApp3/pom.xml
in 8 ms
15:05:40.209 [Worker-15] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed:
[/testApp3/pom.xml]
15:05:40.212 [Worker-15] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Project configuration is not up-to-date with pom.xml. Run project configuration
update' on resource '/testApp3'.
15:05:40.258 [Worker-15] DEBUG o.e.m.c.i.p.ProjectConfigurationManager - Updating project
configuration for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml.
15:05:40.258 [Worker-15] DEBUG o.e.m.c.i.p.ProjectConfigurationManager - Setting encoding
for project testApp3: UTF-8
15:05:40.268 [Worker-15] DEBUG o.e.m.c.i.p.ProjectConfigurationManager - Updated project
configuration for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml in 10 ms.
15:05:40.268 [Worker-15] INFO o.e.m.c.i.p.ProjectConfigurationManager - Project import
completed 0 sec
15:05:40.356 [Worker-8] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: []
15:05:40.359 [Worker-8] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: []
15:05:40.587 [Worker-15] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh
request: [/testApp3/pom.xml]
15:05:40.899 [Worker-15] DEBUG o.e.m.c.i.builder.MavenBuilder - Building project testApp3
15:05:40.900 [Worker-15] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing:
[/testApp3/pom.xml]
15:05:40.902 [Worker-15] DEBUG o.e.m.c.internal.embedder.MavenImpl - Reading Maven
project: /home/ldimaggi/git/testApp3/pom.xml
15:05:40.908 [Worker-15] DEBUG o.e.m.c.internal.embedder.MavenImpl - Read Maven project:
/home/ldimaggi/git/testApp3/pom.xml in 6 ms
15:05:40.908 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IEditorMarkerService
15:05:40.915 [Worker-15] DEBUG o.e.m.c.i.l.LifecycleMappingFactory - Loading lifecycle
mapping for MavenProject: testApp3:testApp3:1.0 @ /home/ldimaggi/git/testApp3/pom.xml.
15:05:40.919 [Worker-15] INFO o.e.m.c.i.l.LifecycleMappingFactory - Using DEFAULT
lifecycle mapping for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml.
15:05:40.919 [Worker-15] DEBUG o.e.m.c.i.l.LifecycleMappingFactory - Loaded lifecycle
mapping in 4 ms for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml.
15:05:40.919 [Worker-15] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources (execution:
default-resources, phase: process-resources)' on resource
'/testApp3/pom.xml'.
15:05:40.920 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:40.920 [Worker-15] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile,
phase: compile)' on resource '/testApp3/pom.xml'.
15:05:40.921 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:40.921 [Worker-15] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-resources-plugin:2.4.3:testResources (execution:
default-testResources, phase: process-test-resources)' on resource
'/testApp3/pom.xml'.
15:05:40.923 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:40.923 [Worker-15] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (execution:
default-testCompile, phase: test-compile)' on resource '/testApp3/pom.xml'.
15:05:40.924 [Worker-15] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:40.925 [Worker-15] DEBUG o.e.m.c.i.p.r.DefaultMavenDependencyResolver - Resolving
dependencies for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml
15:05:40.925 [Worker-15] DEBUG o.e.m.c.internal.embedder.MavenImpl - Reading Maven
project: /home/ldimaggi/git/testApp3/pom.xml
15:05:40.926 [Worker-15] DEBUG o.e.m.c.internal.embedder.MavenImpl - Read Maven project:
/home/ldimaggi/git/testApp3/pom.xml in 1 ms
15:05:40.926 [Worker-15] DEBUG o.e.m.c.i.p.r.DefaultMavenDependencyResolver - Resolved
dependencies for MavenProject: testApp3:testApp3:1.0 @ /home/ldimaggi/git/testApp3/pom.xml
in 1 ms
15:05:40.926 [Worker-15] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed:
[/testApp3/pom.xml]
15:05:41.223 [Worker-15] DEBUG o.e.m.c.p.c.AbstractCustomizableLifecycleMapping - Build
participants for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml
15:05:41.224 [Worker-15] DEBUG o.e.m.c.p.c.AbstractCustomizableLifecycleMapping - Mojo
execution key: org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources (execution:
default-resources, phase: process-resources)
15:05:41.224 [Worker-15] DEBUG o.e.m.c.p.c.AbstractCustomizableLifecycleMapping - Mojo
execution key: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution:
default-compile, phase: compile)
15:05:41.224 [Worker-15] DEBUG o.e.m.c.p.c.AbstractCustomizableLifecycleMapping - Mojo
execution key: org.apache.maven.plugins:maven-resources-plugin:2.4.3:testResources
(execution: default-testResources, phase: process-test-resources)
15:05:41.224 [Worker-15] DEBUG o.e.m.c.p.c.AbstractCustomizableLifecycleMapping - Mojo
execution key: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile
(execution: default-testCompile, phase: test-compile)
15:05:41.224 [Worker-15] DEBUG o.e.m.c.p.c.AbstractCustomizableLifecycleMapping - Mojo
execution key: org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (execution:
default-test, phase: test)
15:05:41.225 [Worker-15] DEBUG o.e.m.c.p.c.AbstractCustomizableLifecycleMapping - Mojo
execution key: org.apache.maven.plugins:maven-war-plugin:2.1.1:war (execution:
default-war, phase: package)
15:05:41.225 [Worker-15] DEBUG o.e.m.c.p.c.AbstractCustomizableLifecycleMapping - Mojo
execution key: org.apache.maven.plugins:maven-install-plugin:2.3.1:install (execution:
default-install, phase: install)
15:05:41.225 [Worker-15] DEBUG o.e.m.c.p.c.AbstractCustomizableLifecycleMapping - Mojo
execution key: org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (execution:
default-deploy, phase: deploy)
15:05:41.225 [Worker-15] DEBUG o.e.m.c.i.builder.MavenBuilder - Built project testApp3 in
325 ms
15:05:41.588 [Worker-6] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing:
[/testApp3/pom.xml]
15:05:41.593 [Worker-6] DEBUG o.e.m.c.internal.embedder.MavenImpl - Reading Maven project:
/home/ldimaggi/git/testApp3/pom.xml
15:05:41.612 [Worker-6] DEBUG o.e.m.c.internal.embedder.MavenImpl - Read Maven project:
/home/ldimaggi/git/testApp3/pom.xml in 19 ms
15:05:41.612 [Worker-6] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IEditorMarkerService
15:05:41.623 [Worker-6] DEBUG o.e.m.c.i.l.LifecycleMappingFactory - Loading lifecycle
mapping for MavenProject: testApp3:testApp3:1.0 @ /home/ldimaggi/git/testApp3/pom.xml.
15:05:41.628 [Worker-6] INFO o.e.m.c.i.l.LifecycleMappingFactory - Using DEFAULT
lifecycle mapping for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml.
15:05:41.628 [Worker-6] DEBUG o.e.m.c.i.l.LifecycleMappingFactory - Loaded lifecycle
mapping in 5 ms for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml.
15:05:41.633 [Worker-6] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources (execution:
default-resources, phase: process-resources)' on resource
'/testApp3/pom.xml'.
15:05:41.638 [Worker-6] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:41.641 [Worker-6] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile,
phase: compile)' on resource '/testApp3/pom.xml'.
15:05:41.647 [Worker-6] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:41.650 [Worker-6] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-resources-plugin:2.4.3:testResources (execution:
default-testResources, phase: process-test-resources)' on resource
'/testApp3/pom.xml'.
15:05:41.655 [Worker-6] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:41.658 [Worker-6] DEBUG o.e.m.c.i.markers.MavenMarkerManager - Created marker
'Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (execution:
default-testCompile, phase: test-compile)' on resource '/testApp3/pom.xml'.
15:05:41.663 [Worker-6] WARN o.e.m.c.internal.markers.MarkerUtils - Could not find OSGI
service for org.eclipse.m2e.core.internal.markers.IMarkerLocationService
15:05:41.664 [Worker-6] DEBUG o.e.m.c.i.p.r.DefaultMavenDependencyResolver - Resolving
dependencies for MavenProject: testApp3:testApp3:1.0 @
/home/ldimaggi/git/testApp3/pom.xml
15:05:41.664 [Worker-6] DEBUG o.e.m.c.internal.embedder.MavenImpl - Reading Maven project:
/home/ldimaggi/git/testApp3/pom.xml
15:05:41.665 [Worker-6] DEBUG o.e.m.c.internal.embedder.MavenImpl - Read Maven project:
/home/ldimaggi/git/testApp3/pom.xml in 1 ms
15:05:41.666 [Worker-6] DEBUG o.e.m.c.i.p.r.DefaultMavenDependencyResolver - Resolved
dependencies for MavenProject: testApp3:testApp3:1.0 @ /home/ldimaggi/git/testApp3/pom.xml
in 2 ms
15:05:41.666 [Worker-6] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed:
[/testApp3/pom.xml]
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
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-environm... -->
<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
2:40 p.m.
[
https://issues.jboss.org/browse/JBIDE-10070?page=com.atlassian.jira.plugi...
]
Len DiMaggio updated JBIDE-10070:
---------------------------------
Attachment: JBIDE-10070-Screenshot.png
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-environm... -->
<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
4:59 a.m.
[
https://issues.jboss.org/browse/JBIDE-10070?page=com.atlassian.jira.plugi...
]
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-environm... -->
<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
5:47 a.m.
[
https://issues.jboss.org/browse/JBIDE-10070?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen resolved JBIDE-10070.
-----------------------------------------
Resolution: Rejected
The openshift projects are maven projects that uses web packaging - for eclipse to handle
this you need to have m2e and m2e-wtp installed.
Using JBoss Tools updatesite you get easily by remembering to install JBoss Maven Tools.
If you don't want to do that you can right click the problem marker, chooose Quick Fix
and use the option to go to marketplace and m2e-wtp should come available to you.
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: Max Rydahl Andersen
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-environm... -->
<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
2:59 p.m.
[
https://issues.jboss.org/browse/JBIDE-10070?page=com.atlassian.jira.plugi...
]
Len DiMaggio closed JBIDE-10070.
--------------------------------
No longer reproducible.
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: Max Rydahl Andersen
Fix For: 3.3.0.M5
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-environm... -->
<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
5206
days inactive
5275
days old
jbosstools-issues@lists.jboss.org
5 comments
6 participants
participants (6)
-
Andre Dietisheim (Commented) (JIRA) -
Len DiMaggio (Closed) (JIRA)
-
Len DiMaggio (Commented) (JIRA)
-
Len DiMaggio (Created) (JIRA)
-
Len DiMaggio (Updated) (JIRA)
-
Max Rydahl Andersen (Resolved) (JIRA)