Community
Participate
Working Groups
Driver: 0404N + lastest from jst.j2ee from 04/06 Java classes in the JavaSource directory are not being compiled into the WebContent/WEB-INF/classes directory. The directory does not exist even after explicitly cleaning the project, rebuilding and refreshing. For a project named "CProj" with a module called "c1", here's the .classpath file: <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui. launcher.StandardVMType/j2sdk1.4.2_07"/> <classpathentry kind="con" path="org.eclipse.jst.server.core.container/org.eclipse.jst.server.tomcat.runtim eTarget/Apache Tomcat v5.0"/> <classpathentry output=".deployables/c1/WEB-INF/classes" kind="src" path="c1/JavaSource"/> <classpathentry kind="output" path="bin"/> </classpath>
I can see the classes directory is in the bProj/.deployables/b1/WEB-INF/ directory, not bProj/b1/WEB-INF directory and the Java files are compiled there. However, the bProj/.deployables/b1/WEB-INF/classes directory is not on the build path of the project. This could be similar to the problem in defect 90515 where the JARs in the /WebContent/WEB-INF directory is not on the build path of the project.
Moving to M5 as per our discussion. The ouput classes folder will not be added ot the classpath as anything that lives in ".deployables" is arbitrary to our implementation of the flex project builder and is simply a staging area. We have initial plans of adding api to IVirtualResource to .getContainingOutput(int options) which would return an array of output from a given resource. More info will be provided during early M5.
Also, if project X has dependent project Y, the build path for project X should include the classes directory of project Y. See defect 90957: https://bugs.eclipse.org/bugs/show_bug.cgi?id=90957
*** Bug 90957 has been marked as a duplicate of this bug. ***
Using Eclipse 3.1M7, I see the .deployables folder as an extra Output folder under Project Properties | Java Build Path | Source (tab). However, attempting to remove or modify this Output folder is "reverted" with the next build. In other words, deleting the entry and clicking OK appears successful, but the little bugger magically reappears when the Project Properties are viewed again. I've attempted many combinations including changing the path, toggling "Allow output folders..", and weeping softly, all to no avail.
Created attachment 21713 [details] Illustrates the .deployables output folder NOT going away.
.deployables is going away once the server side is done w/ their publish tasks. At that point i can forward you api to access the output location of source folders....they will be in Project/bin/componentName folders now. Look for this end of this week early next *** This bug has been marked as a duplicate of 97756 ***
Changed Version field given new release numbering.
Closing. We will use defect 92259 to react to the change to .deployable.
