Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 45209 - plugin building does not take into account linked folder
Summary: plugin building does not take into account linked folder
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 3.0 M9   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-20 09:50 EDT by Adrian Spinei CLA
Modified: 2004-04-13 12:51 EDT (History)
0 users

See Also:


Attachments
the plugin.xml example (14.15 KB, application/octet-stream)
2003-10-20 09:52 EDT, Adrian Spinei CLA
no flags Details
.classpath file featuring the linked folder (4.26 KB, application/octet-stream)
2003-10-20 09:52 EDT, Adrian Spinei CLA
no flags Details
corresponding build.properties (641 bytes, text/plain)
2003-10-20 09:53 EDT, Adrian Spinei CLA
no flags Details
the generated build.xml (9.18 KB, application/octet-stream)
2003-10-20 09:54 EDT, Adrian Spinei CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Spinei CLA 2003-10-20 09:50:56 EDT
Take for instance a plugin project, which is using libraries from a linked
folder (defined as a directory "commonlibs" in the root of the plugin project).
The build.xml and classpath are generated just fine and the project compiles.
However, multiple problems appear :
- when running a workbench with the plugin in question Eclipse seems to have
lost track of all jars referenced from the linked folder. Only jars really
existing into the project are visible.
- as expected, the generated Ant task does not seem to understand where the
commonlibs plugin is pointing. I was expecting a replacement of the linked
folder name with the real path, then the creation of a "commonlibs" directory
containing the referenced jars in order to include it in the plugin archive.
Thus, usage of linked folders proves un-useable for PDE build process.
Workbench running correctly would be a bare minimum, and a custom Ant script
could eventually fix the second issue.
Comment 1 Adrian Spinei CLA 2003-10-20 09:52:06 EDT
Created attachment 6484 [details]
the plugin.xml example
Comment 2 Adrian Spinei CLA 2003-10-20 09:52:45 EDT
Created attachment 6485 [details]
.classpath file featuring the linked folder
Comment 3 Adrian Spinei CLA 2003-10-20 09:53:43 EDT
Created attachment 6486 [details]
corresponding build.properties
Comment 4 Adrian Spinei CLA 2003-10-20 09:54:29 EDT
Created attachment 6487 [details]
the generated build.xml
Comment 5 Pascal Rapicault CLA 2004-04-13 12:51:27 EDT
When used in stand alone mode, pde build now take into account the link folder.
Fixed in HEAD.