Summary: | netbeans crashs if creating a new java class | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas, Berlinghoff <schwupp-diwupp> |
Component: | [OLD] Development | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | iyosifov |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Thomas, Berlinghoff
2005-07-10 15:20:38 UTC
Could you please run netbeans-4.0 from command line and post if it outputs something. I can reproduce this with 4.1 but not with 4.0. (In reply to comment #1) > Could you please run netbeans-4.0 from command line and post if it outputs > something. I can reproduce this with 4.1 but not with 4.0. Sorry, but there's no output :( Mfg Sino Ok, I've currently downloaded the sources (Same as emerge does) and compiled it by myself. I mostly do the same as the ebuild does, except the following: 209: unset DISPLAY 215: export ANT_OPTS="${ANT_OPTS} -Xmx1g -Djava.awt.headless=true" sun-jdk-1.4.2_08 ismy system wide JVM. After the compilation was done, netbeans works fine for me. Perhaps the exported ANT_OPTS makes trouble ? Anyway, I am currently on my laptop (Had the problem mentioned above on two machines (my laptop and my normal computer)) but I'll apply the changes to the ebuild and try it again on my normal computer. Hope that helps. (In reply to comment #3) > > After the compilation was done, netbeans works fine for me. Perhaps the exported > ANT_OPTS makes trouble ? The environment is reset after the ebuild is done. So ANT_OPTS is not left to the environment. You can check this by running env | grep ANT_OPTS. Could you please try my improved ebuild in the experimental tree: https://gentooexperimental.org/svn/java/gentoo-java-experimental/dev-util/netbeans It has fixes to other issues. At least with this version I am unable to reproduce your problem. I will be testing with the 4.1 ebuild to find out more. I've currently tried both ebuilds contained on your page, unfortunatelly none of them works. 1. Start netbeans (4.0 shows Error messages in the lower left corner, 4.1 doesn't) 2. When creating a java class, the program locks up and must be killed (4.0 as well as 4.1) Mfg Sino Well, got netbeans-4.1 working when comment out some function calls in the ebuild 156 fool_scrambler 202 symlink_extjars ${D}/${DESTINATION} 245 make_desktop_entry netbeans-${SLOT} Netbeans netbeans Development So 4.1 works well for me now. Haven't had time to take a closer look on the called functions (So I didn't really now what they are good for), but I'll do it if I got some spare time. [url]http://sinotech.dyndns.org/netbeans-4.1.ebuild[/url] Mfg Sino Ok, here are my next results. I've activated the following lines again 245 make_desktop_entry netbeans-${SLOT} Netbeans netbeans Development and it still works. After that I reactivated the following line: 202 symlink_extjars ${D}/${DESTINATION} and the program locks (And must be killed) when creating a new project. Then I've deactivated it again, and tried to activate some part of the "fool_scrambler" function. After that, when creating a project, a window appears, disappears, appears again and so on. So there must be a problem in "symlink_extjars" as well as in the first part of "fool_scrambler". Here's the build I've tried: http://sinotech.dyndns.org/netbeans-4.1.ebuild I've put the line "# HERE HERE HERE HERE" into "fool_scrambler". Things above the line caused the problem I described above, the things aren't tested yet (Will do that tomorrow). Anyway, since I've got no ebuild for tomcat-5.5, I've changed the dependency to "tomcat-5.0.28". But since I've just tried to create a simple "Java apllication"-project, it shouldn't matter, should it ? Mfg Sino HAVE CHANGED: the things aren't tested yet (Will do that tomorrow). TO: the things below aren't tested yet (Will do that tomorrow). Ok, here are my next results. I've activated the following lines again 245 make_desktop_entry netbeans-${SLOT} Netbeans netbeans Development and it still works. After that I reactivated the following line: 202 symlink_extjars ${D}/${DESTINATION} and the program locks (And must be killed) when creating a new project. Then I've deactivated it again, and tried to activate some part of the "fool_scrambler" function. After that, when creating a project, a window appears, disappears, appears again and so on. So there must be a problem in "symlink_extjars" as well as in the first part of "fool_scrambler". Here's the build I've tried: http://sinotech.dyndns.org/netbeans-4.1.ebuild I've put the line "# HERE HERE HERE HERE" into "fool_scrambler". Things above the line caused the problem I described above, the things below aren't tested yet (Will do that tomorrow). Anyway, since I've got no ebuild for tomcat-5.5, I've changed the dependency to "tomcat-5.0.28". But since I've just tried to create a simple "Java apllication"-project, it shouldn't matter, should it ? Mfg Sino See the following link to check out the whole experimental tree. http://gentoo-wiki.com/Experimental_Java_tree It seems that there are problems with the linking to the system jars. I have already fixed some issues with 4.1 and will continue tomorrow. I will post here after I have committed my stuff to the experimental tree. OK, I've already downloaded that experimental tree and installed the "tomcat-5.5" package. I've also done some little testings (Try and error ;) ) with my current netbeans-4.1 ebuild. Therefore I figured out two little parts which will cause the problems: In function "fool_scrambler()" the following lines: 283 cd ${S}/mdr/external/ 284 unscramble_and_empty 285 java-pkg_jar-from ${JMI} 286 java-pkg_jar-from ${MOF} and in function "symlink_extjars()" the following lines cd ${1}/ide${IDE_VERSION}/modules/ext 366 java-pkg_jar-from ${COMMONS_LOGGING} 367 java-pkg_jar-from flute 368 java-pkg_jar-from ${JMI} 369 java-pkg_jar-from ${JUNIT} 370 java-pkg_jar-from ${MOF} 371 java-pkg_jar-from sac One of them causes the program locks up when creating a new project, the other one caused a little window to appear, disappear, ... (Like described above). I've also put the ebuild file again on my little webserver: file:///usr/local/portage_over/dev-util/netbeans/netbeans-4.1.ebuild Mfg Sino Here the right URL: http://sinotech.dyndns.org/netbeans-4.1.ebuild (Lines I've deactivated, are enclose by "# BUG BUG BUG BUG" Ok, think the problem is caused by ${JMI} and ${MOF} variables. I've deactived the lines where they're used, and then netbeans-4.1 run fine. So these are the lines I've deactivated: function fool_scrambler: 285 java-pkg_jar-from ${JMI} 286 java-pkg_jar-from ${MOF} function symlink_extjars: 370 java-pkg_jar-from ${JMI} 372 java-pkg_jar-from ${MOF} Updated ebuild can be found here: http://sinotech.dyndns.org/netbeans-4.1.ebuild Mfg Sino I've tried re-merging "dev-java/jmi-interface" ("jmi.jar" and "mof.jar" are part of this package) but it doesn't change anything. Anyway, just seen that netbeans-4.1 shows up error messages (I said it doesn't a few posts above). Haven't seen it since it wasn't in the lower left corner as in version 4.0 (Now it's a little red icon in the lower right corner). It also says that there's a log file in "~/.netbeans/4.1/var/log". If you need to see it, it is here: http://sinotech.dyndns.org/messages.log Mfg Sino Found the reason. mof.jar in jmi-interface doesn't include mof.xml which is included in the Netbeans version of mof.jar. Updates for Netbeans and jmi-interface are coming soon. Ok. The ebuilds in the experimental should now be fixed. We will be looking at moving them to the main tree tomorrow. (In reply to comment #15) > Ok. The ebuilds in the experimental should now be fixed. We will be looking at > moving them to the main tree tomorrow. Nice to hear. I'll wait for that. Mfg Sino 4.0-r2 is now in the tree. Please, update all the dependencies and test. Reopen if the problem still exists. Excellent job all around! Had this bug until I updated to 4.0-r2. Now everything works perfectly. Just follow the tutorial for converting from 3.6 to 4.0 to create projects and there are no problems. I'm even able to define external JAR files that are necessary and use them properly. |