Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322280 - Export does not properly resolve linked resources
Summary: Export does not properly resolve linked resources
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Libra (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 322943 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-10 15:46 EDT by Cole Markham CLA
Modified: 2022-02-24 11:24 EST (History)
3 users (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 Cole Markham CLA 2010-08-10 15:46:49 EDT 
Build Identifier: CVS Head

If a project is not stored in the workspace directory then the WAR Product Export does not properly resolve the web.xml, launch.ini or any included libraries. This most likely also happens when using linked resources in Helios.

The problem is that the paths are resolved by appending to the workspace filesystem location, rather than using the Resources framework to resolve properly.

Validation exists for libraries, but not for web.xml or launch.ini, but that is really a separate bug. For this bug, validation is broken on the libraries because it uses the same logic to resolve against the workspace location.

Reproducible: Always

Steps to Reproduce:
1. Import an existing project into workspace, don't select "Copy into workspace"
2. Reference the launch.ini, web.xml, or library in the war product
3. Validation errors for libraries, missing files for the others.
Comment 1 Holger Staudacher CLA 2010-08-17 18:29:47 EDT 
Fixed in CVS HEAD.
Comment 2 Karsten Voigt CLA 2010-08-18 08:54:02 EDT 
*** Bug 322943 has been marked as a duplicate of this bug. ***