[Riyad Kalla]

juba, thank you for posting a fix, I’m glad it’s working again.

[Michael Laccetti]

I would classify it as a workaround, but good to know until ME fully supports Maven.

Edit:
I couldn’t get that to work. The only way I can work around it is to close the project that is depended upon. =\

[Ashutosh Jindal]

I was able to solve this problem, and even though the problem may be specific to my setup, here it is.

Short Version of the solution:
One of my projects had export=”true” for all it’s jars. For eg:

<classpathentry exported="true" kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

removing the exported=”true” for all the classpathentry elements in the .classpath file solved the problem

LONG Version of the solution:
My Workspace consists of one webapp which depends on 11 other java projects. I am not sure what happened but one fine day I started getting the ‘Deployment Failure’ error for this webapp. I tried out the following things, none of which worked:
1. Reinstalled Myeclipse 5.1.1
2. Tried creating a new workspace

A webapp created from scratch would deploy fine, just not _my_ webapp X( . That led me to the conclusion that there had to be something wrong with one of my projects. I removed all project dependencies from the webapp and started adding them one by one each time deploying the webapp. Finally, found the project which was the culprit. I got a clean copy of that project from the repository and voila ! it worked .. !!
On comparison .. I found that the problem was the .classpath file of that project. All the jars in the problematic classpath file had export=”true”. As soon as I added these the deployment error reappeared. And removing these entried allowed the deployment to run fine

Here is the text of the ‘bad’ .classpath file:

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
    <classpathentry kind="src" path="src"/>
    <classpathentry exported="true" kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
    <classpathentry exported="true" kind="var" path="JBOSS_CLIENT/jboss-j2ee.jar"/>
    <classpathentry exported="true" kind="var" path="JBOSS_CLIENT/log4j.jar"/>
    <classpathentry exported="true" kind="var" path="JBOSS_CLIENT/concurrent.jar"/>
    <classpathentry exported="true" kind="var" path="JBOSS_ROOT/jboss-common.jar"/>
    <classpathentry exported="true" kind="var" path="JBOSS_ROOT/jboss-jmx.jar"/>
    <classpathentry exported="true" kind="var" path="JBOSS_ROOT/jboss-system.jar"/>
    <classpathentry exported="true" kind="var" path="JBOSS_SERVER/jboss.jar"/>
    <classpathentry exported="true" kind="var" path="JBOSS_SERVER/jmx-adaptor-plugin.jar"/>
    <classpathentry exported="true" kind="var" path="JBOSS_SERVER/jbossmq.jar" sourcepath="JBOSS_SRC"/>
    <classpathentry exported="true" kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
    <classpathentry kind="output" path="output/classes"/>
</classpath>

And what follows is the text from the working .classpath file:

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
    <classpathentry kind="src" path="src"/>
    <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
    <classpathentry kind="var" path="JBOSS_CLIENT/jboss-j2ee.jar"/>
    <classpathentry kind="var" path="JBOSS_CLIENT/log4j.jar"/>
    <classpathentry kind="var" path="JBOSS_CLIENT/concurrent.jar"/>
    <classpathentry kind="var" path="JBOSS_ROOT/jboss-common.jar"/>
    <classpathentry kind="var" path="JBOSS_ROOT/jboss-jmx.jar"/>
    <classpathentry kind="var" path="JBOSS_ROOT/jboss-system.jar"/>
    <classpathentry kind="var" path="JBOSS_SERVER/jboss.jar"/>
    <classpathentry kind="var" path="JBOSS_SERVER/jmx-adaptor-plugin.jar"/>
    <classpathentry kind="var" path="JBOSS_SERVER/jbossmq.jar" sourcepath="JBOSS_SRC"/>
    <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
    <classpathentry kind="output" path="output/classes"/>
</classpath>

Hope this helps!

[Michael Laccetti]

This message has not been recovered.

[Ashutosh Jindal]

This message has not been recovered.

[Ueland]

I just encountered the problem and reason was pretty simple:
-A external jar was used in the build path for the project, the problem was that the file was missing, so MyEclipse responded with that message. So the problem is simply that MyEclipse reports the wrong problem. 🙂

[acuretra]

I am investigating this same problem in MyEclipse 6.0.1, and the error message is still as unhelpful. Sigh

[Riyad Kalla]

acuretra,
We did add Maven support to MyEclipse in 6.5, I don’t know if that helps you out at all (although the project layout still has to be the classic MyEclipse project layout for the most part).

[acuretra]

@acuretra wrote:

I am investigating this same problem in MyEclipse 6.0.1, and the error message is still as unhelpful. Sigh

I found the cause of my problem. I had java projects without a source folder, so the output folder wasn’t being built. This missing folder causes an exception to be thrown when building a PACKED war file (I guess the unpacked deployment is just silently swallowed)

[snowpix]

I have still the same problem. When I disable “Maven Dependency Managment” everything is working fine.
Is there maybe a log-file where I can see which file causes the problem?

[Riyad Kalla]

snowpix,
Any issues should be logged to your <workspace dir>\.metadata\.log file, it’s appended to the bottom, so try and reproduce the issue then check the log file for new entries.

[Author]

Posts