Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326240

Summary:	Tomcat integration not adding .jar files from library and second source directory to deployment
Product:	[WebTools] WTP ServerTools	Reporter:	Dean Schulze <dean_w_schulze>
Component:	wst.server	Assignee:	Larry Isaacs <larryisaacs>
Status:	RESOLVED WORKSFORME	QA Contact:	Angel Vera <arvera>
Severity:	major
Priority:	P3	CC:	remy.suen
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Dean Schulze

2010-09-25 15:32:52 EDT

Build Identifier: 20100617-1415

I created a dynamic web project and added a second source directory (a conf/ dir in my project) and several external .jar files to the library.  When I deployed to Tomcat using the Tomcat integration none of the .jar files I added to the libraries got deployed.

I have a similar project that deploys properly and when I compared the org.eclipse.wst.common.component files the first project has the external .jar files listed as <dependent-module .../>.  It also has the second source directory as a <wb-resource .../> (the conf/ directory in my project), while the defective project does not.

The Tomcat integration doesn't reliable add external .jar files or additional source directories to the org.eclipse.wst.common.component file.

Reproducible: Sometimes

Steps to Reproduce:
1.  Create dynamic web project
2.  Add external .jar files to library.  Add additional source directories
3.

Comment 1 Angel Vera

2011-02-16 11:20:32 EST

Not sure if this belongs to us or the J2EE team. Larry over to you

Comment 2 Larry Isaacs

2011-02-16 15:08:32 EST

I would highly recommend trying Eclipse 3.6.1/WTP 3.2.2, such as the Java EE Developer SR1 package.  I have vague recollections of the Deployment Assembly page having issues in the initial release of WTP 3.2.0.  Certainly, something that isn't listed in the org.eclipse.wst.common.component file isn't going to be published (given the exception that entries in the ".classpath" file can be tagged for publishing).  Why intended changes aren't getting in there is unknown, and isn't something I recall happening to me.  If you are able to reproduce this with WTP 3.2.2, please provide exact steps so we can attempt to reproduce.  Thanks.

Comment 3 Larry Isaacs

2011-04-07 13:22:01 EDT

Marking as WORKSFORME since there isn't enough information to determine what is going wrong.  This bug can be re-opened when there is more information about the exact steps to reproduce.