Summary: | dev-util/netbeans-6.7_rc3 launcher doesn't error out on a JDK not able to handle NB bytecode | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maciej Józiewicz <maciek.joziewicz> |
Component: | [OLD] Development | Assignee: | Miroslav Šulc <fordfrog> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | dev-tools, java |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maciej Józiewicz
2009-06-22 21:31:44 UTC
My guess is that you have ant compiled using jdk 6, but you use jdk 5 to run netbeans. Run netbeans using jdk 6 and check whether the problem is still there. I changed the system-vm from 1.5 to 1.6 using eselect and now it works. Thanks :) Don't you think that a message about that after emerging netbeans would do good? This can occur to any app. Imagine situation that you compile some app with dependencies, dependencies are java5, app is java5. Then you recompile some dependency to java6 bytecode. This breaks your app, but it happens after emerge. So even a message on app emerge would not catch this. Then, maybe a message in the VMs ebuilds? So that noobs like me know what's going on. (In reply to comment #3) > This can occur to any app. Imagine situation that you compile some app with > dependencies, dependencies are java5, app is java5. Then you recompile some > dependency to java6 bytecode. This breaks your app, but it happens after > emerge. So even a message on app emerge would not catch this. > Yes but normally gjl when launching things will notice the need for a higher JDK and will switch accordingly. You should add checking to the Netbeans launcher for launching it with a JDK that can't handle the bytecode in the Netbeans dependency tree or Netbeans itself. netbeans does not use launcher at all, has no package.env file and does not use ebuild functions to symlink compilation and runtime jars so jars are not registered in the dep tree. It it done this way for year or more, because after some changes in eclasses it was not possible to correctly work with dependencies in case of netbeans ebuilds. Unfortunately I do not recall the details. I just know that eclass functions reported some errors. If I switch netbeans to launcher, that would only fix problem when netbeans is compiled using jdk 6 and run using jdk < 6, but would not fix this problem with ant. |