[acuretra]

I had the pleasure of being unable to build a web project pulled out from the attic, with the very non-descriptive “Deployment failed” message. After a bit of investigation I found the .log file where the exception is logged if a PACKED deployment is built (for some reason not the unpacked one).

It turned out that my problem was that I was dependent on library projects which SINCE I worked with the mother project had their source folder removed from the build path (as CVS required a file to be in there to be extracted, and that file was reduntant so the “Create JAR” command failed on other projects. Removing the source folder cured THAT problem).

Unfortunately the J2EE deployment fails with this exception:

!ENTRY com.genuitec.eclipse.ast.deploy.core 1 0 2008-06-30 15:28:29.491
!MESSAGE Build Exception
!STACK 0
com.genuitec.eclipse.core.GenuitecCoreException: Resource ‘/jakarta-commons-beanutils-1.7.0/bin’ does not exist.
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.privExportWebProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.exportWebProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentPackager.exportWebProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.WebDeployment.deployAsPackageArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizard$2.run(Unknown Source)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Caused by: org.eclipse.core.runtime.CoreException: Resource ‘/jakarta-commons-beanutils-1.7.0/bin’ does not exist.
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer$1.run(Unknown Source)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1779)

It is clearly seen that it considers the non-presense of an output folder to be A Very Bad Thing, which it isn’t when you don’t have any source folders.

Could this requirement be loosened up a bit, please?

/Thorbjørn

[Loyal Water]

Your project can’t NOT have an output dir, it’s an Eclipse project requirement.

You can go to Project > Properties > Java BuildpAth > Source and point at some output dir.

[acuretra]

Sure the project has an output dir (as can be seen from the exception message), but apparently if there is no source folders for the project that folder is not being recreated after the project is cleaned.

Hence, it is possible to have a registerered output folder (as is clearly seen from the above) which is not present on disk. I have worked around this by having a source folder with a dummy item in it for each project containing only library jars so the output folder is created and the MyEclipse deployment can succeed.

[Loyal Water]

Sure the project has an output dir (as can be seen from the exception message), but apparently if there is no source folders for the project that folder is not being recreated after the project is cleaned.

Now I understand what you have pointed out. An eclipse project needs to have a scr folder declared as a part of its structure but I’ll make a note of your request and pass it to the management.

[acuretra]

It is certainly possible to have a Java project without a source folder. Just try removing the sourcefolder from the build path after creating a blank java project.

[Author]

Posts