Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » ServerTools (WTP) » Forcing existing project into WTP
Forcing existing project into WTP [message #520273] Thu, 11 March 2010 19:14
sp  is currently offline sp Friend
Messages: 4
Registered: March 2010
Junior Member
I have a rather complicated project setup with many wars and a non-traditional layout of the j2ee project.
I am using ant to do the builds. I am trying to get rid of the build deploy test cycle which takes a long time. So I am thinking of moving my project to WTP.
I managed to make one of my java projects into WTP by adding dynamic web project facet. And I have added multiple source files and directories to the .component file. Its unable to deploy and I am slowly trying to get it to pick up classes by modifying the file

For a start the file looks like this
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="myproj">
<wb-resource deploy-path="/" source-path="/j2ee_apps/myproj.war/web-app"/>
<wb-resource deploy-path="/WEB-INF" source-path="/j2ee-apps/myproj.war/web-app/WEB-INF"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/java"/>
<wb-resource deploy-path="/WEB-INF/lib" source-path="/j2ee-apps/myproj.war/web-app/WEB-INF/lib"/>

<wb-resource deploy-path="/WEB-INF/lib" source-path="/online.ear/onlinelib/classes.jar"/> 

<property name="context-root" value="myproj"/>


Can someone point me to good documentation on the .component file and how it interacts with the .classpath.

I am going to have to build this by hand since the project structure we have is rather loopy.
Previous Topic:Galileo: How to persist faces-config page-flow
Next Topic:Java EE dependencies not added to lib
Goto Forum:

Current Time: Sun Mar 07 00:12:22 GMT 2021

Powered by FUDForum. Page generated in 0.01690 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top