254676 – <library-directory> specified not created in ear

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

Bug 254676 - <library-directory> specified not created in ear

Summary: <library-directory> specified not created in ear

Status:	RESOLVED DUPLICATE of bug 241466

Alias:	None

Product:	WTP Java EE Tools
Classification:	WebTools
Component:	jst.j2ee (show other bugs)
Version:	3.1
Hardware:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	jst.j2ee
QA Contact:	Chuck Bridgham

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2008-11-08 06:31 EST by Paul Rooney
Modified:	2008-11-10 06:51 EST (History)
CC List:	1 user (show)

See Also:

Attachments
ear.jpg (59.30 KB, image/jpeg) 2008-11-08 06:32 EST, Paul Rooney	no flags	Details
proj_explorer.jpg (53.35 KB, image/jpeg) 2008-11-08 06:32 EST, Paul Rooney	no flags	Details
View All 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 Paul Rooney

2008-11-08 06:31:12 EST

Build ID: 3.4.1

Steps To Reproduce:
1. Create 'enterprise app project' and normal java project 

2. On ear project, in 'Java EE Module Dependencies' add the project and tick 'in lib dir'. Then 'change library directory' to something other than default.
See attachment proj_explorer.jpg

3. choose 'Run On Server' on the ear project and deploy to app server (Jboss 5 rc2)


More information:
Check contents of created ear, observe that eclipse didn't create the defined <library-directory> directory but rather it just stored the utility jar in the root of the ear.

see attachment ear.jpg

Comment 1 Paul Rooney

2008-11-08 06:32:08 EST

Created attachment 117391 [details]
ear.jpg

Comment 2 Paul Rooney

2008-11-08 06:32:51 EST

Created attachment 117392 [details]
proj_explorer.jpg

Comment 3 Kaloyan Raev

2008-11-10 06:51:44 EST

Thanks for the screenshots. 
Looks to be the same as bug 241466. 

*** This bug has been marked as a duplicate of bug 241466 ***