|Importing existing web project with Callisto [message #172817]
||Sat, 01 July 2006 07:03
Originally posted by: ale.sarco.com.ar|
I downloaded the last Eclipse release 3.2, and installed to a new directory. Then I installed WTP through the Callisto upgrade site, but when I try to import an existing web project that I've been using for months with Eclipse 3.1x and WTP 1.0x, the new WTP doesn't seems to detect my WebContent directory, so the Web App Libraries is empty and obviously all the jars in WEB-INF/lib are not in the classpath and the project won't build.
I spent a lot of time, but I couldn't find a way to explicitely tell WTP to use WebContent directory for... er... WebContent.
|Re: Importing existing web project with Callisto [message #172824 is a reply to message #172817]
||Sat, 01 July 2006 21:29
Originally posted by: wrose.zip-it.org|
This may be a dupe if the news server has a 12-hour+ lag, but I think my
last post just didn't get through.
I just wanted to add a 'me too' to this problem and give some extra info.
I get the same problem (Web App Libraries no longer automatically
populates from WEB-INF-/lib) even after:
* deleting and re-creating the Web App Libraries entry in the build path
* changing the name of the .settings/.content to
* trying to import the project from my old workspace into a new 3.2
* trying to checkout the project freshly from CVS
Curiously, the web application seems to find the /WEB-INF directory as it
can build the list of servlets/filters/listeners etc with correct
information, so it must have found the deployment descriptor.
Is this a side effect of missing the memo on necessary steps to upgrade?
Powered by FUDForum
. Page generated in 0.10191 seconds