Cannot deploy j2ee projects with MyEclipse when 0.0.10 of Maven Eclipse Plugin is installed

MyEclipse Details:

*** Date: 
Friday, April 13, 2007 12:21:08 PM CDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_07

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 5.5.0 Milestone 2
Build id: 20070409-5.5.0-Milestone2

*** Eclipse details:
Eclipse SDK
Version: 3.2.2
Build id: M20070212-1330

Eclipse Graphical Editing Framework
Version: 3.2.2.v20070208
Build id: 20070208-1315

Eclipse Platform
Version: 3.2.2.r322_v20070119-RQghndJN8IM0MsK
Build id: M20070212-1330

Eclipse Java Development Tools
Version: 3.2.2.r322_v20070104-R4CR0Znkvtfjv9-
Build id: M20060921-0945

Eclipse Graphical Editing Framework
Version: 3.2.2.v20070208
Build id: 20070208-1315

Eclipse Project SDK
Version: 3.2.2.r322_v20070104-dCGKm0Ln38lm-8s
Build id: M20070212-1330

Eclipse RCP
Version: 3.2.2.r322_v20070104-8pcviKVqd8J7C1U
Build id: M20060629-1905

Eclipse Plug-in Development Environment
Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20060921-0945

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\tools\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
ff8_a0
-vm
C:\tools\jdk1.5.0_07\bin\javaw.exe

I also posted this message on the MyEclipse forum:

http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-16783.html

I have the same problem as Kurt. I also have MyEclipse and the 0.0.10 version installed. When I had the 0.0.9 version everything worked fine, but when I upgraded the deploy started to fail.

I also have this issue using MyEclipse 5.5.1 and have also posted to the same forum topic at MyEclipse as mentioned above. I can run from the command line fine, but get this in the console in eclipse.

[INFO] Scanning for projects...
[INFO] ----------------------------------------------------------------------------
[INFO] Building batch-capture
[INFO] task-segment: [test]
[INFO] ----------------------------------------------------------------------------
[ERROR] project-execute : crown:batch-capture:jar:0.3.0 ( task-segment: [test] )
Diagnosis: Error configuring: org.apache.maven.plugins:maven-clean-plugin. Reason: Unable to parse the created DOM for plugin configuration
FATAL ERROR: Error executing Maven for a project
[ERROR] reactor-execute : C:\Java\work\trunk\batch-capture
Diagnosis: Error configuring: org.apache.maven.plugins:maven-clean-plugin. Reason: Unable to parse the created DOM for plugin configuration
FATAL ERROR: Error executing Maven for a project
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-clean-plugin:2.1.1

Cause: Error loading class 'org.apache.maven.plugin.clean.Fileset'
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Fri May 25 10:59:09 EDT 2007
[INFO] Final Memory: 2M/4M
[INFO] ------------------------------------------------------------------------
[INFO] Error for project: batch-capture (during test)
[INFO] ------------------------------------------------------------------------
[INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-clean-plugin:2.1.1

Cause: Error loading class 'org.apache.maven.plugin.clean.Fileset'
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[ERROR] reactor-execute : C:\Java\work\trunk\batch-capture
FATAL ERROR: Error executing Maven for a project
[INFO] BUILD ERRORS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Fri May 25 10:59:09 EDT 2007
[INFO] Final Memory: 2M/4M
[INFO] ------------------------------------------------------------------------

You can try with latest dev build from update site at http://m2eclipse.codehaus.org/update-dev/

Unfortunately we don't have resources to test with MyEclipse. Please escalate this to MyEclipse support. Also see this wiki page that should help to prepare test project for reproducing issue. http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues

Anyways, we'll be glad to accept patch if anyone figure out what is that caused this issue.

I've once again tested this in MyEclipse 6.0.1, Eclipse 3.3.1 and M2 0.0.11 and still no change.

Niklas, I'm nobody official - just another m2eclipse user, but perhaps you should try the 0.0.12 release that was just released over the weekend.

Just to clarify. We won't be looking at this issue unless somebody contribute a test project that would allow us to reproduce this. See the following page for some hints. http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues

Also, it it is anyhow specific to MyEclipse you may want to request support from the vendor, because we won't be able to fix those.

It's been discovered how to reproduce this issue over on the myeclipse forums, but so far no one knows what to fix.

Given a maven project in myeclipse that produces A.jar, and another maven project that produces B.war, and B.war depends on A.jar, a look in the package explorer will show a folder in the maven dependencies for A.jar. When this folder is the dependency, B.war will not deploy successfully.

If you close the A.jar project, the folder dependency dissapears from the maven dependencies list for B.war and is replaced by the A.jar from the local repository. Now you can successfully deploy B.war.

I can duplicate this issue using MyEclipse version 6.0.1, and m2eclipse plugin version 0.0.11.20070916-2300 loaded from the m2eclipse update site.

Closing because we don't have enough information to reproduce issue. Please feel free to reopen and provide test project and any additional steps required to reproduce this. See wiki for some hints.

Also note that m2eclipse provides project configuration extension points that can be used to configure vendor specific projects. Please request MyEclipse to support those extension points.