Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326212 - Deployment assembly in Project Properties does not copy a new dependency
Summary: Deployment assembly in Project Properties does not copy a new dependency
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: 3.2.3   Edit
Assignee: Rob Stryker CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-24 19:18 EDT by Sergio Eduardo CLA
Modified: 2010-10-21 08:36 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergio Eduardo CLA 2010-09-24 19:18:23 EDT
Build Identifier: 20100617-1415

Import a Web Project with JAR libs referenced (not in web-inf/lib) from previous eclipse version - Galileo;
Add a new classpath entry;
that classpath entry doesn't get copied to server into /WEB-INF/lib automatically and there isn't a option to mark that entry as a J2EE Dependency, as we used to see on Galileo (J2EE Dependency).

There is a strange behavior... watching the .classpath all dependencies that already exists (supposing we're just importing a project configured on Galileo) are shown this way:
<classpathentry kind="lib" path="W:/lib/displaytag/v1.2/displaytag-1.2.jar">
		<attributes>
			<attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>
		</attributes>
	</classpathentry>

and the get copied NORMALLY!
but I've just added a new dependency and eclipse doesn't update correctly the file .classpath:
<classpathentry kind="lib" path="W:/lib/poi/v3.2/poi-3.2.jar">
        <attributes>
            <attribute name="org.eclipse.jst.component.dependency" value="../"/>
        </attributes>
    </classpathentry>

difference: value="../"    ->    value="/WEB-INF/lib"


Reproducible: Always
Comment 1 Sergio Eduardo CLA 2010-09-24 19:25:43 EDT
if it isn't a bug, that feature is not so obvious to use as the one we had on previous Eclipse version - Galileo
Comment 2 Sergio Eduardo CLA 2010-09-27 15:56:36 EDT
I've made a new test... 
- create a new web project;
- add an external referenced lib to classpath (Project Properties / Java Build Path / Libraries / Add External JARs...);
- the brand new depency doesn't get copied into server's deploy folder;
So I choose:
- Project Properties;
- Go to "Deployment Assembly" tab
- Click "Add..." Button;
- Choose a reference type "Referenced Projects Classpath Entries"
- Choose the same library choosen on previous step

Originally, the classpath entry, was like <classpathentry kind="lib" path="W:/lib/struts/atual/struts.jar" />

After the update on "Deployment Assembly": 
<classpathentry kind="lib" path="W:/lib/struts/atual/struts.jar">
		<attributes>
			<attribute name="org.eclipse.jst.component.dependency" value="../"/>
		</attributes>
	</classpathentry>

But, still that dependency, doesnt't get copied into right place... even after clean command and full publish of the server...
Comment 3 Carl Anderson CLA 2010-10-15 16:55:14 EDT
Assigning to Rob for initial investigation.
Comment 4 Sergio Eduardo CLA 2010-10-16 06:47:33 EDT
I've just downloaded this version:

Version: Helios Service Release 1
Build id: 20100917-0705

and it seems that the bug has been resolved... I will make a new test later, importing the projects and observing the behavior...

Thank you,
Sergio
Comment 5 Sergio Eduardo CLA 2010-10-21 08:36:29 EDT
The bug has been resolved on 
Version: Helios Service Release 1
Build id: 20100917-0705

Thank you all for your support.