Community
Participate
Working Groups
I experienced some additional unwanted and annoying behaviour. If I create a second source folder for my TestCases named "testing", then my sources of the standard source folder "JavaSource" will not be compiled anymore. Only the TestCases are compiled, but into the wrong folder if I set the default output folder to a folder of my choice (but leaving the separate output folder of JavaSource to .deployables). Strange, huh? But everything works if I change the default output folder to .deployables and set a separate output folder for my testcases. Maybe my explanation is some kind of strange, too. Ask I you got some questions. I will surely answer! Andreas
Ok, I have to correct myself. Nothing works. I thought it would but it doesn't. Here is what I did, I made a "clean" for my project, re-compiled the sources and started my xdoclet-task. All went fine my classes are compiled in the correct folders. Now I run my project with tomcat (with RunAs->Run on server), tomcat started up and all was fine, but then I clicked some links and suddenly some exception messages appeared on the console. A javax.servlet.jsp.JspException said it cann't resolve a type which was a few seconds ago in the classes folder of .deployables. But it was, and now it isn't! I cann't believe my compiled classes are gone not all but some of them, I dont know why. This is much stranger than the first bug I discovered. Please help! This is annoying and I don't know how to go on. regards, Andreas
This will be fixed as part of the removal of the .deployables folder and moving back to just bin as the output. Both source folders should be included by using more standard JDT build processes. *** This bug has been marked as a duplicate of 97756 ***
This bug was moved to 'closed' state, since it is so old and since it is a dup, worksforme, invalid bug that its unlikely to still be useful or need further attention. Feel free to re-open, or open a new bug, if this semi-automatic processing was done in error.
