Community
Participate
Working Groups
Created attachment 125169 [details] demo-application, which reproduces the bug Build ID: I20080617-2000 Steps To Reproduce: 1.adjust Properties in build.properties, such as baseLocation points to a valid Eclipse Installation in 3.4.0. 2. just run build.xml with target pde-build 3.produces java.io.FileNotFoundException: ...\base\eclipse\plugins\org.eclipse.pde.build_3.4.0.v20080604\scripts\productBuild\base\eclipse\plugins\org.eclipse.pde.build_3.4.0.v20080604\scripts\productBuild\productBuild.xml baseLocation in somewhat doubled into the path right after the productBuild-Folder. More information: There is absolutely no problem with absolute paths.
The buildDirectory property doesn't seem to support paths with spaces (not uncommon in Windows), either. These limitations can be worked around, but it does make the whole PDE build setup look a bit hackish...
Eric, if your problem isn't specific to a relative buildDirectory, can you please open a new bug with details and the error you see. With the exception of bug 272769, the test suite passes when run in a directory with spaces (which implies a build directory with spaces). Similarly, export from a workspace with spaces also implies a buildDirectory with spaces.
You're right, paths with spaces work fine (the spaces-related problem was self-inflicted, while attempting to fix the build file to handle relative paths). In any case, it appears that to make the build script handle a relative buildDirectory, only the following two additions are required: ... <property name="buildLocation" location="${buildDirectory}"/> ... <target name="build"> <java classname="org.eclipse.equinox.launcher.Main" ...> ... <arg value="-DbuildDirectory=${buildLocation}"/> ... </java> </target>
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. Please reopen, if you plan to provide a fix.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
