[jira] Created: (MEVENIDE-671) Integrated Maven (2.1-SNAPSHOT) fails to build GWT/Maven builds, but 2.0.9 Maven works as expected.

Integrated Maven (2.1-SNAPSHOT) fails to build GWT/Maven builds, but 2.0.9 Maven works as expected.
---------------------------------------------------------------------------------------------------

                 Key: MEVENIDE-671
                 URL: http://jira.codehaus.org/browse/MEVENIDE-671
             Project: mevenide
          Issue Type: Bug
          Components: mevenide-netbeans
    Affects Versions: NB_FUTURE
         Environment: uname -a
Linux nomad-ii 2.6.26.5-45.fc9.i686 #1 SMP Sat Sep 20 03:45:00 EDT 2008 i686 athlon i386 GNU/Linux

java -version
java version "1.6.0"
OpenJDK  Runtime Environment (build 1.6.0-b09)
OpenJDK Client VM (build 1.6.0-b09, mixed mode)

Netbeans 6.5 Beta (but the EXACT same problem occurs under 6.1)

Maven integration: Version: 4.0.2

Embedded Maven version: 2.1-SNAPSHOT

GWT Version: 1.5.2




            Reporter: Jim Powers
            Assignee: Milos Kleint
             Fix For: NB_FUTURE


Using NetBeans Maven2 integration building GWT (Google Web Toolkit) apps with embedded (2.1-SNAPSHOT) Maven fails, but external 2.0.9 build succeeds.

Here's the output.

Scanning for projects...
org.apache.maven.lifecycle.LifecycleSpecificationException:
No lifecycle phase binding can be found for goal: gwt,
specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-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: com.totsp.gwt:maven-googlewebtoolkit2-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.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructBuildPlan(NBBuildPlanner.java:65)
        at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlan(DefaultBuildPlanner.java:67)
        at org.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructInitialProjectBuildPlan(NBBuildPlanner.java:41)
        at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlans(DefaultBuildPlanner.java:56)
        at org.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructInitialProjectBuildPlans(NBBuildPlanner.java:48)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:138)
        at org.netbeans.modules.maven.embedder.exec.MyLifecycleExecutor.execute(MyLifecycleExecutor.java:72)
        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.netbeans.modules.maven.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:216)
        at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
[ERROR]Maven cannot calculate your build plan, given the following information:
[ERROR]Tasks:
[ERROR]Current project:
[ERROR]Group-Id: net.drr
[ERROR]Artifact-Id: test-gwt
[ERROR]Version: 1.0-SNAPSHOT
[ERROR]From file: /home/jim/java_projects/test-gwt/pom.xml
[ERROR]Error message:
[ERROR]No lifecycle phase binding can be found for goal: gwt,
[ERROR]specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
[ERROR]This plugin was resolved successfully.
[ERROR]However, the mojo metadata it contains does not specify a default lifecycle phase binding.
[ERROR]Please provide a valid <phase/> specification for execution: default
[ERROR]in plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
[ERROR]Root error message:
[ERROR]No lifecycle phase binding can be found for goal: gwt,
[ERROR]specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
[ERROR]This plugin was resolved successfully.
[ERROR]However, the mojo metadata it contains does not specify a default lifecycle phase binding.
[ERROR]Please provide a valid <phase/> specification for execution: default
[ERROR]in plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
------------------------------------------------------------------------
For more information, run with the -e flag
------------------------------------------------------------------------
BUILD FAILED
------------------------------------------------------------------------
Total time: 1 second
Finished at: Fri Oct 03 08:32:36 GMT-05:00 2008
Final Memory: 44M/106M
------------------------------------------------------------------------


Notes: using external Maven does work, but since it is not possible to use external maven and debug apps (claims it needs to use internal maven for that) debugging is impossible.  Possible to either address the above problem (although may be bug in Maven 2.1 or GWT Maven plugin, will log bugs at appropriate locations as well), or make it possible to debug apps while using external maven.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

    http://xircles.codehaus.org/manage_email

     [ http://jira.codehaus.org/browse/MEVENIDE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint resolved MEVENIDE-671.
-----------------------------------

    Resolution: Fixed

Wel, I've had continuous problems with the embedded builds for multitude of reasons. It's not 100% compatible with latest release, it has bugs, plugins are not written to be embeddable.

In the post-6.5 beta development builds I've sacked the embedder for building the project. I will first use the user's choice of maven binary to use (if set in Tools/Options), if not set, then I will try to find any maven instance on the computer's PATH. only if not found here, I will use the embedded version, but with a warning at the start of the build output.

I'm marking the issue as fixed as I've changed the workflow in the codebase to avoid embedded builds. If you insist on usign them, please file a bug report against maven or the gwt plugin.

> Integrated Maven (2.1-SNAPSHOT) fails to build GWT/Maven builds, but 2.0.9 Maven works as expected.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-671
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-671
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide-netbeans
>    Affects Versions: NB_FUTURE
>         Environment: uname -a
> Linux nomad-ii 2.6.26.5-45.fc9.i686 #1 SMP Sat Sep 20 03:45:00 EDT 2008 i686 athlon i386 GNU/Linux
> java -version
> java version "1.6.0"
> OpenJDK  Runtime Environment (build 1.6.0-b09)
> OpenJDK Client VM (build 1.6.0-b09, mixed mode)
> Netbeans 6.5 Beta (but the EXACT same problem occurs under 6.1)
> Maven integration: Version: 4.0.2
> Embedded Maven version: 2.1-SNAPSHOT
> GWT Version: 1.5.2
>            Reporter: Jim Powers
>            Assignee: Milos Kleint
>             Fix For: NB_FUTURE
>
>
> Using NetBeans Maven2 integration building GWT (Google Web Toolkit) apps with embedded (2.1-SNAPSHOT) Maven fails, but external 2.0.9 build succeeds.
> Here's the output.
> Scanning for projects...
> org.apache.maven.lifecycle.LifecycleSpecificationException:
> No lifecycle phase binding can be found for goal: gwt,
> specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-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: com.totsp.gwt:maven-googlewebtoolkit2-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.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructBuildPlan(NBBuildPlanner.java:65)
>         at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlan(DefaultBuildPlanner.java:67)
>         at org.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructInitialProjectBuildPlan(NBBuildPlanner.java:41)
>         at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlans(DefaultBuildPlanner.java:56)
>         at org.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructInitialProjectBuildPlans(NBBuildPlanner.java:48)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:138)
>         at org.netbeans.modules.maven.embedder.exec.MyLifecycleExecutor.execute(MyLifecycleExecutor.java:72)
>         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.netbeans.modules.maven.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:216)
>         at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
> [ERROR]Maven cannot calculate your build plan, given the following information:
> [ERROR]Tasks:
> [ERROR]Current project:
> [ERROR]Group-Id: net.drr
> [ERROR]Artifact-Id: test-gwt
> [ERROR]Version: 1.0-SNAPSHOT
> [ERROR]From file: /home/jim/java_projects/test-gwt/pom.xml
> [ERROR]Error message:
> [ERROR]No lifecycle phase binding can be found for goal: gwt,
> [ERROR]specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> [ERROR]This plugin was resolved successfully.
> [ERROR]However, the mojo metadata it contains does not specify a default lifecycle phase binding.
> [ERROR]Please provide a valid <phase/> specification for execution: default
> [ERROR]in plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> [ERROR]Root error message:
> [ERROR]No lifecycle phase binding can be found for goal: gwt,
> [ERROR]specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> [ERROR]This plugin was resolved successfully.
> [ERROR]However, the mojo metadata it contains does not specify a default lifecycle phase binding.
> [ERROR]Please provide a valid <phase/> specification for execution: default
> [ERROR]in plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> ------------------------------------------------------------------------
> For more information, run with the -e flag
> ------------------------------------------------------------------------
> BUILD FAILED
> ------------------------------------------------------------------------
> Total time: 1 second
> Finished at: Fri Oct 03 08:32:36 GMT-05:00 2008
> Final Memory: 44M/106M
> ------------------------------------------------------------------------
> Notes: using external Maven does work, but since it is not possible to use external maven and debug apps (claims it needs to use internal maven for that) debugging is impossible.  Possible to either address the above problem (although may be bug in Maven 2.1 or GWT Maven plugin, will log bugs at appropriate locations as well), or make it possible to debug apps while using external maven.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MEVENIDE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149806#action_149806 ]

Jim Powers commented on MEVENIDE-671:
-------------------------------------

Milos,

Thanks for your comment.

No, I certainly do not insist on using the embedded Maven for sure.  My real issue is that I just want to be able to debug.  If I can use the external maven that is really cool by me, in fact preferable, as 2.0.9 is what we are going to deploy on our continuous integration server and not 2.1-SNAPSHOT.  Better support of the external maven, including the ability to debug, is really much preferable as it means more control over our build environment.  Is something like the ability to debug using external maven-built projects I could expect to see soon?  If not, then I'm kinda stuck and would have to consider dropping the use of NetBeans altogether, which I would prefer not to, as other aspects of Maven integration are rather superb.

> Integrated Maven (2.1-SNAPSHOT) fails to build GWT/Maven builds, but 2.0.9 Maven works as expected.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-671
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-671
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide-netbeans
>    Affects Versions: NB_FUTURE
>         Environment: uname -a
> Linux nomad-ii 2.6.26.5-45.fc9.i686 #1 SMP Sat Sep 20 03:45:00 EDT 2008 i686 athlon i386 GNU/Linux
> java -version
> java version "1.6.0"
> OpenJDK  Runtime Environment (build 1.6.0-b09)
> OpenJDK Client VM (build 1.6.0-b09, mixed mode)
> Netbeans 6.5 Beta (but the EXACT same problem occurs under 6.1)
> Maven integration: Version: 4.0.2
> Embedded Maven version: 2.1-SNAPSHOT
> GWT Version: 1.5.2
>            Reporter: Jim Powers
>            Assignee: Milos Kleint
>             Fix For: NB_FUTURE
>
>
> Using NetBeans Maven2 integration building GWT (Google Web Toolkit) apps with embedded (2.1-SNAPSHOT) Maven fails, but external 2.0.9 build succeeds.
> Here's the output.
> Scanning for projects...
> org.apache.maven.lifecycle.LifecycleSpecificationException:
> No lifecycle phase binding can be found for goal: gwt,
> specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-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: com.totsp.gwt:maven-googlewebtoolkit2-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.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructBuildPlan(NBBuildPlanner.java:65)
>         at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlan(DefaultBuildPlanner.java:67)
>         at org.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructInitialProjectBuildPlan(NBBuildPlanner.java:41)
>         at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlans(DefaultBuildPlanner.java:56)
>         at org.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructInitialProjectBuildPlans(NBBuildPlanner.java:48)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:138)
>         at org.netbeans.modules.maven.embedder.exec.MyLifecycleExecutor.execute(MyLifecycleExecutor.java:72)
>         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.netbeans.modules.maven.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:216)
>         at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
> [ERROR]Maven cannot calculate your build plan, given the following information:
> [ERROR]Tasks:
> [ERROR]Current project:
> [ERROR]Group-Id: net.drr
> [ERROR]Artifact-Id: test-gwt
> [ERROR]Version: 1.0-SNAPSHOT
> [ERROR]From file: /home/jim/java_projects/test-gwt/pom.xml
> [ERROR]Error message:
> [ERROR]No lifecycle phase binding can be found for goal: gwt,
> [ERROR]specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> [ERROR]This plugin was resolved successfully.
> [ERROR]However, the mojo metadata it contains does not specify a default lifecycle phase binding.
> [ERROR]Please provide a valid <phase/> specification for execution: default
> [ERROR]in plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> [ERROR]Root error message:
> [ERROR]No lifecycle phase binding can be found for goal: gwt,
> [ERROR]specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> [ERROR]This plugin was resolved successfully.
> [ERROR]However, the mojo metadata it contains does not specify a default lifecycle phase binding.
> [ERROR]Please provide a valid <phase/> specification for execution: default
> [ERROR]in plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> ------------------------------------------------------------------------
> For more information, run with the -e flag
> ------------------------------------------------------------------------
> BUILD FAILED
> ------------------------------------------------------------------------
> Total time: 1 second
> Finished at: Fri Oct 03 08:32:36 GMT-05:00 2008
> Final Memory: 44M/106M
> ------------------------------------------------------------------------
> Notes: using external Maven does work, but since it is not possible to use external maven and debug apps (claims it needs to use internal maven for that) debugging is impossible.  Possible to either address the above problem (although may be bug in Maven 2.1 or GWT Maven plugin, will log bugs at appropriate locations as well), or make it possible to debug apps while using external maven.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MEVENIDE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149810#action_149810 ]

Milos Kleint commented on MEVENIDE-671:
---------------------------------------

yes, in the dev builds I removed the requirement on doing debug/deploy with embedded maven only. So debugging shall work with command line maven as well now.
Actually you can now debug the maven build itself
Setting the "jpda.listen=maven" property in the relevant Action goal mapping (in project properties Actions panel) will make the IDE integration to generate a correct MAVEN_OPTS setting  and attach itself to the build. That's useful when you need to debug something that's executed in the same VM as maven build itself. No UI for now, later will add a checkbox in the Actions panel for it.

You can try the dev builds, t should be close to RC so the quality shall be at least comparable to beta. Maven support is no update center.
http://bits.netbeans.org/download/trunk/nightly/latest/

> Integrated Maven (2.1-SNAPSHOT) fails to build GWT/Maven builds, but 2.0.9 Maven works as expected.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-671
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-671
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide-netbeans
>    Affects Versions: NB_FUTURE
>         Environment: uname -a
> Linux nomad-ii 2.6.26.5-45.fc9.i686 #1 SMP Sat Sep 20 03:45:00 EDT 2008 i686 athlon i386 GNU/Linux
> java -version
> java version "1.6.0"
> OpenJDK  Runtime Environment (build 1.6.0-b09)
> OpenJDK Client VM (build 1.6.0-b09, mixed mode)
> Netbeans 6.5 Beta (but the EXACT same problem occurs under 6.1)
> Maven integration: Version: 4.0.2
> Embedded Maven version: 2.1-SNAPSHOT
> GWT Version: 1.5.2
>            Reporter: Jim Powers
>            Assignee: Milos Kleint
>             Fix For: NB_FUTURE
>
>
> Using NetBeans Maven2 integration building GWT (Google Web Toolkit) apps with embedded (2.1-SNAPSHOT) Maven fails, but external 2.0.9 build succeeds.
> Here's the output.
> Scanning for projects...
> org.apache.maven.lifecycle.LifecycleSpecificationException:
> No lifecycle phase binding can be found for goal: gwt,
> specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-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: com.totsp.gwt:maven-googlewebtoolkit2-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.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructBuildPlan(NBBuildPlanner.java:65)
>         at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlan(DefaultBuildPlanner.java:67)
>         at org.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructInitialProjectBuildPlan(NBBuildPlanner.java:41)
>         at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlans(DefaultBuildPlanner.java:56)
>         at org.netbeans.modules.maven.embedder.exec.NBBuildPlanner.constructInitialProjectBuildPlans(NBBuildPlanner.java:48)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:138)
>         at org.netbeans.modules.maven.embedder.exec.MyLifecycleExecutor.execute(MyLifecycleExecutor.java:72)
>         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.netbeans.modules.maven.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:216)
>         at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
> [ERROR]Maven cannot calculate your build plan, given the following information:
> [ERROR]Tasks:
> [ERROR]Current project:
> [ERROR]Group-Id: net.drr
> [ERROR]Artifact-Id: test-gwt
> [ERROR]Version: 1.0-SNAPSHOT
> [ERROR]From file: /home/jim/java_projects/test-gwt/pom.xml
> [ERROR]Error message:
> [ERROR]No lifecycle phase binding can be found for goal: gwt,
> [ERROR]specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> [ERROR]This plugin was resolved successfully.
> [ERROR]However, the mojo metadata it contains does not specify a default lifecycle phase binding.
> [ERROR]Please provide a valid <phase/> specification for execution: default
> [ERROR]in plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> [ERROR]Root error message:
> [ERROR]No lifecycle phase binding can be found for goal: gwt,
> [ERROR]specified as a part of the execution: defaultin plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> [ERROR]This plugin was resolved successfully.
> [ERROR]However, the mojo metadata it contains does not specify a default lifecycle phase binding.
> [ERROR]Please provide a valid <phase/> specification for execution: default
> [ERROR]in plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin
> ------------------------------------------------------------------------
> For more information, run with the -e flag
> ------------------------------------------------------------------------
> BUILD FAILED
> ------------------------------------------------------------------------
> Total time: 1 second
> Finished at: Fri Oct 03 08:32:36 GMT-05:00 2008
> Final Memory: 44M/106M
> ------------------------------------------------------------------------
> Notes: using external Maven does work, but since it is not possible to use external maven and debug apps (claims it needs to use internal maven for that) debugging is impossible.  Possible to either address the above problem (although may be bug in Maven 2.1 or GWT Maven plugin, will log bugs at appropriate locations as well), or make it possible to debug apps while using external maven.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

    http://xircles.codehaus.org/manage_email