Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366323 - customBuildCallback's safe-apt cannot handle paths with spaces
Summary: customBuildCallback's safe-apt cannot handle paths with spaces
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Sapphire (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Konstantin Komissarchik CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-11 03:57 EST by Roded Bahat CLA
Modified: 2021-11-19 09:22 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roded Bahat CLA 2011-12-11 03:57:51 EST
Build Identifier: 20110916-0149

When exporting a Sapphire plugin which uses customBuildCallBacks.xml and using a sapphire.classpath which contains a space in its path, apt will not use the classpath and the build will fail.
The error produced I've encountered in this case was a NPE in parsing Sapphire's annotations as their class files could not be found.


Reproducible: Always

Steps to Reproduce:
1. Define sapphire.classpath as Eclipse's plugins dir:
<path id="sapphire.classpath">
    <fileset dir="${eclipse.home}/plugins" includes="*.jar"/>
</path>
2. Change the Eclipse directory name so that it contains a space.
3. Export a Sapphire plugin which uses customBuildCallbacks.xml.
Comment 1 Konstantin Komissarchik CLA 2012-05-18 15:24:01 EDT
I was not able to reproduce this issue. I changed customBuildCallBacks.xml in samples plugin to reference a Sapphire repository located at a path with a space in it and was able to export the samples plugin without any errors.
Comment 2 Roded Bahat CLA 2012-05-23 04:41:57 EDT
I tired opening my adopter plugin in dev-eclipse and testing it there. Since it works, this is probably an issue with my eclipse installation.