Community
Participate
Working Groups
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.
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.
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.