Deploy projects dependencies as exploded folder structures instead of jars

[gabron]

Is there a way to tell the deployment assembly for a given project in STS to not jar up a STS project dependency and explode it in the tomcat webapps directory when it deploys. The issue is we have two projects, one is the actual web project and one is a shared project. We have started to use tcServer which requires actually deploying to the web apps directory and ends up jaring up our entire shared project. In the past we would run out of the workspace when we were using plain old Tomcat and didn't seem to have some of the issues we are now running into. I know myeclipse does something like this, I thought STS would do it but I'm not seeing it. Thanks

[Martin Lippert]

Hi!

The tomcat support does this kind of direct workspace deployment (without putting stuff in JARs) using some special classloaders. Unfortunately we don't have that at the moment for tc Server. What you could do instead is maybe using the agent-based reloading feature that we have been working on the past to make updating a running application easier. It allows you to change a lot of stuff while the app in running in tc Server without re-deploying or re-starting the app. Did you try that? Would be interesting to hear if that works for your setting.

Cheers,
-Martin