| Problem with new hardcoded m4 project structure - URGENT!! [message #97020] |
Mon, 02 May 2005 08:31 |
Eclipse User |
|
|
|
Hello,
we have a big problem with the new hardcoded way, m4 is handling its project structure.
In short, it is not possible anymore to define a tomcat-global project and several webapp-scope subprojects.
For all the web projects our company uses one global project, a company own cms.
So every web project has to include this main project.
Since a few of these projects are WebDAV projects, we have to put the cms classes into the folder %TOMCAT_HOME%/common/classes (otherwise they don't get loaded correctly for WebDAV).
With m3, this was not a problem - we just added a linked folder to the cms project, pointing to %TOMCAT_HOME%/common/classes.
Then we defined the project's output folder pointing to this linked folder.
All the other projects had this project on their build path, and with tomcat the classes were available to all projects anyways (common folder).
With m4 it is not possible anymore to change the classes output folder. Whatever you configure in the project properties, the WTP changes it back to MyProject/.deployables/MyModule/WEB-INF/classes.
Not even any modifications to the MyProject/.wtpmodules file bring any help.
Is there any way/workaround to switch off this annoying WTP reconfigure mechanism for a project, so you can define the classes folder by yourself?
Please help, this matter is really urgent - our company can't work on it's web applications anymore!
....unless we switch back to m3 :-(
Thanks,
Chily
|
|
|
Powered by
FUDForum. Page generated in 0.06039 seconds
Home