Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #309157 +++ I20100413-1521 Steps: * In any build.properties files, add an additional output entry that refers to nothing on the bundle classpath. For example: output.some.jar = . * No errors appears even though "some.jar" does not exist on the bundle classpath Errors are properly flagged, however, I get strange secondary error with this patch. For example: * check out "org.eclipse.debug.core" from HEAD * add "source.junk = junk/" to the build.properties I get two errors: An entry for junk/ is required in bin.includes build.properties /org.eclipse.debug.core line 11 Plug-in Problem The specified library 'junk' is not on the plug-in classpath. build.properties /org.eclipse.debug.core line 21 Plug-in Problem The first is wrong.
Created attachment 169220 [details] Patch
Created attachment 169228 [details] update This is an update for this bug and bug 309157. It adds a null check (just to be safe), and changed "plug-in" to "bundle" in the error message.
Fixed as part of bug 309157
There was an extra space in the resource string that was changed. I fixed it in HEAD.
Verified