This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When I start debugging a J2SE project, I get this in the output window: init: deps-jar: compile: Non-existing path "D:\jdk1.5.0_06\jre\lib\i18n.jar" provided. Non-existing path "D:\jdk1.5.0_06\jre\lib\sunrsasign.jar" provided. Non-existing path "D:\jdk1.5.0_06\jre\classes" provided. After that, the project runs normally. I am using a non-default platform for that project. Using q-build "netbeans-5_0-daily-bin-200512182030-18_Dec_2005_2030.zip" with fresh user dir. The project worked fine with NB 5.0 Beta 2.
It seems as someone debug message which should not affect the IDE behaviour. Does the project have unmodified build.xml and build-impl.xml?
Only these additional lines in build.xml: <target name="-do-jar-without-manifest"/> <target name="-do-jar-with-manifest"/> <target name="-do-jar-with-mainclass"/> <target name="-post-clean" depends="init"> <echo message="Deleting all classes from ${build.classes.dir}"/> <delete> <fileset dir="${build.classes.dir}" includes="**/*.class"/> </delete> <echo message="Deleting all classes from ${build.test.classes.dir}"/> <delete> <fileset dir="${build.test.classes.dir}" includes="**/*.class"/> </delete> </target>
Thanks, these changes should be harmless.
Probably not P2, it is only warning message, the functionality is not affected. It is written by the nbjpdastart task to warn user that a part of the classpath does not exist. The i18n.jar, unrsasign.jar, classes/ are reported by the JDK as a part of the bootclasspath, but they don't physically exist in most cases. Fix: The bootclasspath shouldn't probably be checked.
This is just a warning that there are some non-existing items on the class path. In this case it's harmless, since the given jars are actually not used. The fix can really be to skip the verification of the bootclasspath.
The check is disabled for bootclasspath now: /cvs/debuggerjpda/ant/antsrc/org/netbeans/modules/debugger/jpda/ant/JPDAConnect.java,v <-- JPDAConnect.java new revision: 1.20; previous revision: 1.19 /cvs/debuggerjpda/ant/antsrc/org/netbeans/modules/debugger/jpda/ant/JPDAStart.java,v <-- JPDAStart.java new revision: 1.40; previous revision: 1.39
This is fixed only in 5.1? I predict users will file more bug reports about this when 5.0 is released.
Yes, it's fixed only in 5.1. Unfortunately it came late in the release cycle - in high-resistance mode, where only severe bugs can be fixed. This is just a warning about non-existent paths on the classpath and it occurs only when the user selects a different JDK from the JDK on which NetBeans are running. Although the fix is simple, this can not be considered as a high-priority bug according to http://qa.netbeans.org/processes/bug_priority_guidelines.html
Well, this bug was not in Beta 2. It was introduced afterwards, so it is a regression. And it may not stop NB from working perfectly, but it will irritate (new) users for sure.
*** Issue 72823 has been marked as a duplicate of this issue. ***
I still get this "error" with the current 5.5 dev build (200605080500)
Yes, this issue was fixed in dev builds, not in NB 5.5. Only fixes of high-priority defects were ported into NB 5.5.
*** Issue 77524 has been marked as a duplicate of this issue. ***
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.
Created attachment 153170 [details] https://mail.google.com/mail/u/0/#inbox/14cb2a7abc2431d5
Created attachment 153171 [details] https://mail.google.com/mail/u/0/#inbox/14cb2a7abc2431d5
Created attachment 153172 [details] https://mail.google.com/mail/u/0/#inbox/14cb2a7abc2431d5