[mevenide-user] FW: Mevenide2 - Netbeans IDE 6 Integration Questions

IDE:  NetBeans IDE 6.0 (Build 200711261600) /GA

Java:  1.5.0_14-b03

System:  Windows XP

Maven:  2.0.7

 

Hi,

 

First off, I have really enjoyed this plug-in with Netbeans 6.  Working
on  maven-based projects with a lot of dependencies, this plugin has
been a big time saver.  I was shocked how easy it was to setup a large
set of projects.  Thanks to the developers!!

 

We recently split out two logical web sites from one into two war files.
To reuse common code(jsf pages, java classes, and various static
content) that was shared in the web tier, we used the warpath type
dependency in our two deployable .war files:

 

<dependency>

 
<groupId>${pom.parent.groupId}</groupId>

 
<artifactId>WebCommon</artifactId>

 
<version>${pom.parent.version}</version>

                                                <type>war</type>

                                </dependency>

                                <dependency>

 
<groupId>${pom.parent.groupId}</groupId>

 
<artifactId>WebCommon</artifactId>

 
<version>${pom.parent.version}</version>

                                                <type>warpath</type>

                                </dependency>

 

 

After doing this, we've been running into two problems,

 

Issue 1)  We can no longer deploy to glassfish v2 from within IDE or
other 

------------------------------------------------------------------------
----------------

Error resolving version for 'org.appfuse:maven-warpath-plugin': Plugin
requires Maven version 2.0.6

------------------------------------------------------------------------

Trace

org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving
version for 'org.appfuse:maven-warpath-plugin': Plugin requires Maven
version 2.0.6

 

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
LifecycleExecutor.java:1337)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeHand
lers(DefaultLifecycleExecutor.java:1247)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(Defau
ltLifecycleExecutor.java:176)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:141)

        at
org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execute
(MyLifecycleExecutor.java:92)

        at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182)

        at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760)

        at
org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaEx
ecutor.java:196)

        at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)

Caused by:
org.apache.maven.plugin.version.PluginVersionResolutionException: Error
resolving version for 'org.appfuse:maven-warpath-plugin': Plugin
requires Maven version 2.0.6

        at
org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(D
efaultPluginManager.java:258)

        at
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau
ltPluginManager.java:183)

        at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM
anager.java:163)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
LifecycleExecutor.java:1328)

        ... 9 more

------------------------------------------------------------------------

Total time: 4 seconds

Finished at: Mon Feb 04 13:56:20 CST 2008

Final Memory: 72M/169M

------------------------------------------------------------------------

 

 

Issue 2) the java classes in the parent webcommon .war file project
aren't recognized in the IDE.  

------------------------------------------------------------------------
-----------------------------------

It manifests itself as non-recognition of classes (no code completion,
IDE wanting to import or create classes instead of recognizing them.)

 

We are not having similar issues with our dependencies that are
inheriting strictly java classes.  (our business layer projects for
example)  The install target works as expected.  I was thinking about
splitting out the java classes and having a webcommonjava project to try
to overcome the above mentioned problems.  

 

I'd love any options anyone can come up with...  My apologies if I've
missed something obvious... I'm very new to Maven and Netbeans.

 

 

Thanks,

Alan May