Community
Participate
Working Groups
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.
Created attachment 6484 [details] the plugin.xml example
Created attachment 6485 [details] .classpath file featuring the linked folder
Created attachment 6486 [details] corresponding build.properties
Created attachment 6487 [details] the generated build.xml
When used in stand alone mode, pde build now take into account the link folder. Fixed in HEAD.