[pfullarton]

I am working with Eclipse 2.1.2 and MyEclipse 2.6.2. I have a “web project” and I am trying to use the MyEclipse deployment tool to deploy that project to a local Tomcat 4.1.2 instance on the same machine. I’ve enabled the tomcat instance and can start/stop it from Eclipse. I can add the server as a deployment target, but when I try to deploy (as exploded) it makes the new directory in “<tomcat-home>/webapps” but does not copy the project files.

I believe this is because my project contents reside in Eclipse “linked folders” (I didn’t want my project source to sit under my Eclipse installation directory). Is there a known problem with deploying from “linked folders”. Is there a fix or workaround or something I am not doing correctly?

I did see a couple previous postings about folks having issues with linked folders, but I didn’t see a response indicating there had been a fix. It seemed like folks would use Ant to deploy to get around it.

Thanks!
-First time poster and new user, and liking it so far!
-Paul

[Scott Anderson]

Paul,

Yes, there is a problem with full support for linked folders and there is an open bug report on it. We hope to get it resolved in the next release or so. Sorry for the inconvenience.

There is a workaround for you that you might like to fix this:

(I didn’t want my project source to sit under my Eclipse installation directory)

Eclipse can support workspace locations anywhere on your drive. You can simply point to the directory that you’d like Eclipse to use by modifying your launch alias to use the -data command like this:

<path-to-eclipse-exed> -data <path-to-workspace-dir>

I think that will solve your concern nicely and avoid the use of the more complicated linked folder mechanism.

[Author]

Posts