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.
NetBeans IDE Dev (Build 200701301900) 1.5.0_05; Java HotSpot(TM) Client VM 1.5.0_05-b05 Windows XP version 5.1 running on x86 ================================================= At NB Startup, an errro notice pops up looking for file not found: C:\Program Files\netbeans\6.0\200701301900\Files\netbeans\6.0\200701301900\ide8 \modules\ext\jaxws21\api It think it meant to look for: C:\Program Files\netbeans\6.0\200701301900\ide8\modules\ext\jaxws21\api. Notice that "Files\netbeans\6.0\200701301900\" over-appended. I looked at C:\Program Files\netbeans\6.0\200701301900\ide8\modules\ext\jaxws21\api and found two jars: jaxb-api and jaxws-api. This happened after I treated Issue 93847 by deleting the problematic project and recreated it successfully, and then restarting netbeans. Now it shows up everytime I restart netbeans.
Created attachment 37940 [details] Looking for file using over-appended path
Is there in the mentioned project or other locations in IDE (e.g. Favorites Tab, Libraries ...) any reference to this path?
The message comes up even when I start nb with a virgin ide env - i.e. no [C:\Documents and Settings\user\dev] folder, no projects. Therefore no favourites, no tabs, no Libraries, no extra modules. It is still there at Build 200702081900.
Therefore, it is probably unrelated to Issue 93847. It is probably coincidental to my move to build 200701301900.
Hah! I found the problem. I copied the whole netbeans folder to D:/temp/200702081900 At which I ran netbeans and the message did not appear. However the message [D:\temp\Eclipse Sucks\200702081900\Sucks\200702081900\ide8\modules\ext\jaxws21 \api does not exist ....] when I moved and ran netbeans at D:\temp\Eclipse Sucks\200702081900. I tried every instance where path has a space char and the message pops up. Which means, somewhere in NB6 code (for builds on and after 200701301900) is a space-char unfriendly routine.
duplicate *** This issue has been marked as a duplicate of 95796 ***