Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348176 - Dependent projects not getting deployed
Summary: Dependent projects not getting deployed
Status: RESOLVED INVALID
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Rob Stryker CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 04:43 EDT by vishwa.raikar CLA
Modified: 2011-12-22 17:21 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description vishwa.raikar CLA 2011-06-03 04:43:24 EDT 
Build Identifier: 20110218-0911

I have a dynamic web project and 3 java projects. The dynamic web project depends on 3 java projects. I added the project dependencies for web project under Java build path -> Projects under properties. When I publish dynamic web project, the classes of dependent java projects are not deployed under WEB-INF/classes folder. I tried few things like selecting the dependent java projects under "Order and export", adding bin folder of dependent java projects under "Libraries" within Java build path, but nothing helped. The same set up works fine in MyEclipse.

Reproducible: Always

Steps to Reproduce:
1.Have a dynamic web project and few java projects
2.Set java projects as dependent projects for web project
3.Publish the web project
Comment 1 Carl Anderson CLA 2011-06-03 14:53:05 EDT 
vishwa, I assume that, based on your build identifier, you are using Eclipse Helios SR2, which corresponds to WTP 3.2.3.

Have you tried selecting your project, bring up properties, and then select the Deployment Assembly tab?  By using this to include your java projects, it will create jars for them in your Web project's WEB-INF/lib.

Assigning to Rob for initial investigation, if there is anything else left to do.
Comment 2 Rob Stryker CLA 2011-12-22 17:21:35 EST 
It seems to me this bug is a user error. I encourage any user who is still suffering from an error when using the workflow Carl describes to re-open this bug or open a new one.