 |
|
 |
 |
|
 |
 |
| Author |
Message |
|
|
Post subject: Deploy Error When Output Folder is WEB-INF
Posted: Oct 01, 2008 - 10:56 PM
|
|
Registered Member


Joined: May 18, 2005
Posts: 6
|
|
Steps to reproduce:
I started with a brand new installation of 7M2 (All-in-One) on windows.
1. New Web Project (enter project name "dtest"; everything else default)
2. New Class (enter package and name)
3. New source folder "dd"
4. Copied web.xml to "dd"
5. Configure build path
- - Check "Allow output folders for source folders"
- - Set output for "dd" to "WebRoot/WEB-INF/"
6. Click OK
From error log:
!ENTRY org.eclipse.jdt.core 4 4 2008-09-29 14:36:00.130
!MESSAGE JavaBuilder handling ImageBuilderInternalException while building: dtest
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Resource '/dtest/WebRoot/WEB-INF/classes' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:317)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:194)
at org.eclipse.core.internal.resources.Folder.assertCreateRequirements(Folder.java:32)
at org.eclipse.core.internal.resources.Folder.create(Folder.java:88)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.createFolder(AbstractImageBuilder.java:455)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder$1.visit(AbstractImageBuilder.java:252)
at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:58)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:81)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:85)
at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:126)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:68)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.addAllSourceFiles(AbstractImageBuilder.java:217)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:51)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:184)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 org.eclipse.core.resources 4 368 2008-09-29 14:36:00.130
!MESSAGE Resource '/dtest/WebRoot/WEB-INF/classes' does not exist.
See original topic: Error when "Allow output folders for source folders |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Deploy Error When Output Folder is WEB-INF
Posted: Oct 02, 2008 - 08:29 PM
|
|
Registered Member


Joined: Apr 18, 2007
Posts: 5659
|
|
cschofld,
I was able to reproduce the issue that you pointed out. Ill file this for the dev team. Thank you for bringing this up. |
_________________ Nipun
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Nov 11, 2008 - 03:41 PM
|
|
Moderator


Joined: Jan 06, 2004
Posts: 23307
|
|
cschofld,
This is actually expected behavior. By default Eclipse/MyEclipse is setup to "scrub output folder" on a build, if you have our output folder set to WEB-INF, that means the entire contents of that directory is erased before building the project (which includes /lib and /classes, which is why you got the exception).
You can try turning that setting off (shown below) and rebuilding the project a few times, giving MyEclipse a chance to pickup the web.xml file (that it expects in the WEB-INF directory anyway) and close re-open the project and see if it works out. Overall I wouldn't recommend this configuration, but atleast turning off cleaning should allow it to work. |
_________________ Riyad
MyEclipse Support
|
| |
|
|
|
 |
|
|
| |
|
|
 |
|
 |
|
|
|
 |