Community
Participate
Working Groups
Scenario: 1) Create a dummy plugin 2) Right click on generated MANIFEST.MF and Create Ant File build.xml 3) Verify that the target "@dot" exists in build.xml 4) Add the following line to MANIFEST.MF Bundle-ClassPath = bin 5) Re-generate build.xml 6) What should have been "@dot" is now "." In fact everywhere that the directory "@dot" was referenced is now a ".", or it is normalized out of existence... How is this destructive? Don't attempt the "clean" rule as it will delete your plugin! i.e.) The first target in the "clean" rule should be <delete dir="${build.result.folder}/@dot"/> However, what is generated when 'bin' appears in Bundle-ClassPath is: <delete dir="${build.result.folder}"/> As soon as you attempt to perform a clean, your plugin directory will vanish. (And PDE-Build issues a "clean" prior to building) While it might not make sense setting 'bin' on the Bundle-ClassPath, it should not cause the generation of the build.xml to be invalid (and dangerous) Cheers, John
oops, Typo in step 4) should be 4) Add the following line to MANIFEST.MF Bundle-ClassPath: bin Sorry! John
Changed severity from "critical" to "normal" since there is a workaround.
fixed with patch applied with bug 125432
