Community
Participate
Working Groups
make the workDir parameter configurable. there's apparently no (easy) way to set the workDir to a sensible location -- having it in the inards of the workspace's .metadata structure is kind of meaningless in a development environment, isn't it? after all, as a developer one has to look into the generated java classes sometimes and for that purpose it is definitely more sensible to have it at an easily accessed place. i'd prefer to have it in the project itself. having just one workspace and the workDir resembling its structure, setting workDir to $workspace_location would be sufficient for me. there isn't even a paramter to be added to the launch configuration's arguments, it seems. -- Configuration Details -- Product: Eclipse 1.3.2.20110218-0812 (org.eclipse.epp.package.jee.product) Installed Features: org.eclipse.jdt 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
Can you clarify which working directory are you trying to set and the existing metadata setting that you are referring to? It is not clear to me whether it is something belonging to server tools, server launch configuration of a specific server type, WTP project support, eclipse project support or product wide settings.
the workDir parameter of tomcat. afaik there's only one, and it points to the folder where the jsp are converted to java code and compiled to servlets. since stacktraces caused by a jsp always list the generated java code, i need to check the generated code, hence need to find it to begin with. additionally, the wtp is unable to find the genereated java code -- clicking the line in the stacktrace ends with a dialog informing the suer that the file in question cannot be found or is not in the path or something to that effect, and the file is not opened in eclipse.
similar to launch configuration's -> source -> default -> <project> the tomcat workDir needs to be added automatically. after all, the java files generated from JSPs are part of the sources as far as the stacktraces are concerned and the user needs to able to access those files in the same fashion as the Java files in the project itself. it works once the user manually adds this folder, but as I said before, this should happen automatically the same way as the source folders of the project are added when adding the project to the tomcat.
