Re: [mevenide-user] No lifecycle phase binding can be found for goal: exec

I would say that's indeed a bug in the 2.1 embedder. Which hudson
build version are you using? I've recently upgraded the embedder
binaries.

Milos

On Tue, Mar 11, 2008 at 4:20 PM, Putrycz, Erik
<[email protected]> wrote:
>
>
>
>
> This seems to be something new with maven 2.1…
>
> [ERROR]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> construct one or more initial build plans. Reason:
>
>
>
> 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
>
>
>
> [ERROR]           at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>
> [ERROR]           at
> org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execute(MyLifecycleExecutor.java:72)
>
> [ERROR]           at
> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:225)
>
> [ERROR]           at
> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
>
> [ERROR]           at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>
> [ERROR]           at
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:895)
>
> [ERROR]           at
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
>
> [ERROR]           at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>
> [ERROR]           at
> org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:215)
>
> [ERROR]           at
> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
>
> [ERROR]Caused by:
> 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
>
>
>
> My exec plugin is configured as follows
>
>       <plugin>
>
>         <groupId>org.codehaus.mojo</groupId>
>
>         <artifactId>exec-maven-plugin</artifactId>
>
>         <executions>
>
>           <execution>
>
>             <goals>
>
>               <goal>exec</goal>
>
>             </goals>
>
>           </execution>
>
>         </executions>
>
>         <configuration>
>
>           <executable>java</executable>
>
>           <arguments>
>
>             <argument>-Xmx500m</argument>
>
>             <argument>-classpath</argument>
>
>             <!-- automatically creates the classpath using all project
> dependencies,
>
>                  also adding the project build directory -->
>
>             <classpath></classpath>
>
>             <argument>nrc.brex.nav.Navigator</argument>
>
>           </arguments>
>
>         </configuration>
>
>       </plugin>
>
>
>
> I use this plugin for the netbeans "run" action… Is there any way around? I
> don't want the exec to be in any phase.
>
> Btw, the Netbeans GUI is still buggy and forgets any custom setting.
>
>
>
> Erik

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email