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.
Hi, I have a big problem on my Netbeans 6.1, i'm work on MacOs and after install the IReport plugin, my netbeans is broken!!!! When initialize the IDE it's show the next message: "An imcompatible Xalan version has been detected on the IDE's Classpath. The IDE cannot start". Somebody can help me? Thanks. Best Regards Gil Correia
gilcorreira, could you please attach message.log file located in ${netbeans.userdir}/var/log/messages.log (see http://qa.netbeans.org/bugzilla/reportbug.html) as attachment to this issue ? Thanks in advance.
I have the same error after installing some plugins. Looks like it might be due to the jmeter plugin, which includes a xalan.jar in the modules/jmeter/lib directory. find . -name xalan* -print ./libs/xalan.jar ./modules/ext/xalan-2.7.0,jar.old ./modules/ext/xalan.jar ./modules/jmeter/lib/xalan.jar
Created attachment 61209 [details] messages.log
BTW, you might want to add to your FAQ about uploading files from the .netbeans directory, as the browser on Mac doesn't let you get to hidden directories, so you have to cp the file somewhere you can browse in order to upload.
So uninstall the JMeter plugin and file a bug for its author. It is not supported on this website.
So I think I agree with the original poster that this is a bug in that NetBeans flat won't start after the plugin is installed (iReport). Didn't happen to me on Winbloze, so I'm thinking that this is a problem only on OS X. The issue is that after you use the plugins to install this, you can't even start NB. The dialog you get gives you a link to an FAQ that doesn't help (tells you to delete the Xalan jar file from the JRE lib, which doesn't exist). In my case there were several xalan.jar files in the modules directories, but no indication of which would need to be deleted (I tried renaming them as shown in the find from my original post). The FAQ should be updated with how to disable the module that is causing the issue. I was only able to get it to start up after deleting my .netbeans/6.1 subdirectory (which obviously reset everything back to default settings).
I did a quick test and by renaming all of the xalan*.jar files in the .netbeans/6.1 subdirectories except the one in lib, I can get NB 6.1 to load without the error. Didn't try the iReport or JMeter modules to see if they work OK with the version of xalan.jar that is in the .netbeans/6.1/lib directory: find . -name xal* -print ./6.1/libs/xalan.jar ./6.1/modules/ext/xalan-2.7.0.jar.save ./6.1/modules/ext/xalan.jar.save ./6.1/modules/jmeter/lib/xalan.jar.save
Hi, got this problem too : netbeans 5.5.1 and then netbeans 6.1 on Solaris 10 with jdk1.5.0_10. - the FAQ that appears on the popup is no help. Removing the appropriate xalan.jar allows the netbeans to start but then creating a new project fails (at 25%). Sounds likes this issue has been going on for a number of versions - and it's a show stopper - what's going on? rich.
i have the same problem that my ide doesn't start because of the xalan problen in mac os X ,do someone can tell me where exactly are the files that i have to deleted for netbeans to work?, ad start again beacuse everytime i erased does not work.
I removed the following file (from the iReports plugin) and I was able to start NetBeans again. And iReports still seems to work, although I haven't tested very much. (I installed iReports right before this problem showed up.) ~/.netbeans/6.1/modules/ext/xalan.jar
Also, note that "~/.netbeans/6.1/libs/xalan.jar" still exists, so I assume that's where the necessary Xalan-related classes are being found now. Lastly, to "rweaver": Renaming files may fool the NetBeans startup checker, but the checker is trying to avoid that older xalan library for a reason... circumventing the check could cause trouble later?
You missed the point on my rename. I renamed them with a .save suffix, so that NetBeans wouldn't load them. My suggestion is that NB should warn you about the problem in a way that is easier to fix than digging through all the jar files. Ideally it could catch this problem as part of the process of installing the plugin: meaning when NB installs the plugin, have it check the files being installed to see if any of them would cause a problem like this, thereby avoiding the problem of ending up with an unstartable NB.