Surveiller ce forum | Commencer une nouvelle discussion Commencer une nouvelle discussion
[Maven] erreur création mapfishapp [ Répondre ]
Par : Benjamin NORMAND on 2010-01-04 15:07
[forum:472014]
Lors de mes premières tentatives de création de l'application mapfishapp avec maven ( goal : org.codehaus.mojo:exec-maven-plugin:1.1.1:exec ) j'ai eu cette sortie dans la console.

==============================================================
DÉBUT DE CONSLE
==============================================================
[INFO] Scanning for projects...
org.apache.maven.lifecycle.LifecycleSpecificationException:

No lifecycle phase binding can be found for goal: exec,
specified as a part of the execution: defaultin plugin: org.codehaus.mojo:exec-maven-plugin

This plugin was resolved successfully.
However, the mojo metadata it contains does not specify a default lifecycle phase binding.

Please provide a valid <phase/> specification for execution: default
in plugin: org.codehaus.mojo:exec-maven-plugin


at org.apache.maven.lifecycle.binding.DefaultLifecycleBindingManager.getProjectCustomBindings(DefaultLifecycleBindingManager.java:266)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody0(DefaultBuildPlanner.java:99)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody1$advice(DefaultBuildPlanner.java:403)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan(DefaultBuildPlanner.java:1)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlan(DefaultBuildPlanner.java:67)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlans(DefaultBuildPlanner.java:56)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:138)
at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
[ERROR]

Maven cannot calculate your build plan, given the following information:

Tasks:

Current project:
Group-Id: mapfishapp
Artifact-Id: mapfishapp
Version: 1.0
From file: /opt/eclipseWorkSpace/mapfishapp/pom.xml


Error message:

No lifecycle phase binding can be found for goal: exec,
specified as a part of the execution: defaultin plugin: org.codehaus.mojo:exec-maven-plugin

This plugin was resolved successfully.
However, the mojo metadata it contains does not specify a default lifecycle phase binding.

Please provide a valid <phase/> specification for execution: default
in plugin: org.codehaus.mojo:exec-maven-plugin


Root error message:

No lifecycle phase binding can be found for goal: exec,
specified as a part of the execution: defaultin plugin: org.codehaus.mojo:exec-maven-plugin

This plugin was resolved successfully.
However, the mojo metadata it contains does not specify a default lifecycle phase binding.

Please provide a valid <phase/> specification for execution: default
in plugin: org.codehaus.mojo:exec-maven-plugin





[INFO] ------------------------------------------------------------------------
[INFO] For more information, run with the -e flag
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILED
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Mon Jan 04 14:07:09 CET 2010
[INFO] Final Memory: 1M/4M
[INFO] ------------------------------------------------------------------------
==============================================================
FIN DE CONSLE
==============================================================


Aprés quelques recherche et une modification du POM.xml comme suit, j'ai reussi à créer l'application.
J'ai rajouté la ligne "<phase>exec</phase>" entre "<execution>" et "<goals>", ce qui donne :


==============================================================
DÉBUT DU POM.XML
==============================================================
<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>mapfishapp</groupId>
<artifactId>mapfishapp</artifactId>
<packaging>war</packaging>
<version>1.0</version>
<name>mapfishapp Maven Webapp</name>
<url>http://maven.apache.org</url>
......
......
......
<plugin>
<!-- http://mojo.codehaus.org/exec-maven-plugin/ -->
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.1</version>
<executions>
<execution>
<phase>exec</phase>
<goals>
<goal>exec</goal>
</goals>
</execution>
</executions>
<configuration>
<executable>jsbuild/build.sh</executable>
<!--
<arguments>
</arguments>
-->
</configuration>
</plugin>
</plugins>
</build>
</project>
==============================================================
FIN DU POM.XML
==============================================================

Je ne sais pas si c'est la meilleure résolution à ce problème, merci si possible de confirmer.

FEDER Powered By FusionForge Collaborative Development Environment Charte d'utilisation / Nous contacter / Mentions légales Haut de page