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.
Product Version = Forte for Java, CE v. 4.0-EA (Build 020301_1) IDE Versioning = IDE/1 spec=1.43.2 impl=020301_1 Operating System = Linux version 2.4.10 running on i386 Java; VM; Vendor = 1.4.0; Java HotSpot(TM) Client VM 1.4.0-b92; Sun Microsystems Inc. Java Home = /usr/java/j2sdk1.4/sun/jdk1.4/jre System Locale; Encod. = cs_CZ; ISO-8859-2 (f4j_ce) =========================================================================== Well, each FS is represented by its icon and by mounting path in the Explorer's Filesystems TAB. The same I expect when I invoke the FileSystems' customizer (right click on the top node "Filesystems" in the Filesystems TAB of the Explorer and choose cutomize). But here (see the snapshot) GenericVCS filesystems are represented by XML icon with very user unvrendly name like "org-netbeans-modules-...." Could you please make it to look similar as others FSs like JavaCVS FS(the most relative for yours FS)?
Created attachment 4965 [details] snapshot of FS customizer and GenVCS node
oups...sorry I put it on wrong component:-( transvering to genericvcs....
ufff....reassigning to the component owner
This is a strange problem. I've found issue #16951, which is fixed, but apparently the problem persists.
Check issue #19491. If the problem goes away when the XML code module is disabled, then this is probably a duplicate of that issue (in which case you should apply more pressure to get that fixed).
Resolving as duplicate of issue #19491. If I understand it correctly, there is no way for our FS to make it work if XML is installed. It might be solved by looks. *** This issue has been marked as a duplicate of 19491 ***
Okay, this is a duplicate, however it needs to be fixed.
Suggestions: - fix issue #22628 - use setPreferredLoader to ask for org.openide.loaders.XMLDataObject
Cool! It's finally fixed. It was fixed by the fix of issue #22628, which describes essentially the same problem. Thus it perhaps should be a duplicate of issue #22628.
*** This issue has been marked as a duplicate of 22628 ***
Wow, great. This was veery loong story and I am glad to see it fixed now. Thank you Davide ! Verified in development build #200206260100 of NetBeans 3.4.
Resolved for 3.4.x or earlier, no new info since then -> closing.