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.
Using 0925 with jdk1.4, and getting; ----------------------------- Command Refresh failed. Check the full output of the command on the Runtime tab in Explorer. The error output follows: 'cd" "' is not recognized as an internal or external command, operable program or batch file. ----------------------------- I have this same project in another userdir and when running under 0925 with jdk1.3 - this does not occur. It seems this is unique to jdk1.4. Could this be attended to please. Kind reagrds Emmanuel
Created attachment 2694 [details] ide log
On restarting NB this disappears and project back to normal. However, then when switching to another project and back, same proplem re-occurs.
I think that the 1.4jdk is responsible for it and there's a bugtraq issue for it (should be fixed til next beta/fcs). However I'm not 100% sure it's the case, so leaving the decision to close it to Martin.
Definetely. You are right Milos. This is a duplicate of another P1 bug and I would also like to ask you Emmanuel to carefully assing compone- net because there is no vcscvs module included in recent builds so this bug should be filed against vcsgeneric. Don't report any issues on vcscvs next time except if you download this module from Update Center. Thank you a lot. *** This issue has been marked as a duplicate of 14035 ***
Hello Jiri, Thank you for your feedback. I admit, I usually do not know against which module exactly to post an issue. With time, it'll probably become clearer. Back to the issue, I looked at the Sun jdk1.4 issue; http://developer.java.sun.com/developer/bugParade/bugs/4479699.html I'm not exactly sure what everything I read there means, however, it seems it was fixed for jdk1.4 beta2, and/or that a workaround exists or is required. Could the matter be investigated further, seeing as I would need to fall out of the dev builds using jdk1.4, at least until this is resolved either in next beta - although as I read it, beta2 is already fixed, or when NB applies necessary coding, viz., either the workaround, or whatever is 'required for jdk1.4'. Please advise. Kind regards Emmanuel
Hello Emmanuel, firstly, you were looking at wrong bug. Correct one is this: http://developer.java.sun.com/developer/bugParade/bugs/4491217.html Secondly, this bug is already fixed in recent build of JDK 1.4 Beta 3 build #80 but this build has a lot of other serious bugs that avoid its serious usage. We have to wait till b81 is promoted and check it there. This Runtime.exec() issue was not fixed in any of JDK 1.4 Beta 2 builds. So if you want use #80 of Beta 3 or wait for next one. Hope this helps.
Hello Jiri, Thank you for your feedback. >This Runtime.exec() issue was not fixed in any of JDK 1.4 Beta >2 builds. Thank you for clarifying. >So if you want use #80 of Beta 3 or wait for next one. Could you please assist me with this - where do I find these builds, or when the beta3 is scheduled for release, etc.? Kind regards Emmanuel
Well, I can't help you much with this because the site where you can download the latest release of JDK 1.4 is http://java.sun.com/j2se/ but I did not realise that you have to wait approximately one month till Beta 3 is released. It is planned for end of October.
Resolved for 3.4.x or earlier, no new info since then -> closing.