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.
I am using maven 2.0 and Nb6.0b1 with JDK 1.6. I have about 70 Projects using freeForm. The jdk for projects is set to 1.4. I have set the java source level to 1.4. If I build the project, it will compile fine, but the IDE displays some classes with an error symbol as if there was a compile error. The Problem is that the IDE uses default jdk (1.6) instead of the jdk set in freeforms (in this case 1.4) This happens only with freeforms and not with projects created in netbeans. In order to produce this bug please create a java class in maven freeform project that extends e.g. java.io.Writer, so in JDK 1.4 there is an no abstract method like abstract append(char). In JDK 1.6 there is an Appendable interface. So you have no chance, your IDE displays the class red with an Errormessage that abstract append(char) is not implemented and if you click on java.io.Writer class you will be forward to jdk 1.6 java src. Apperently NetBeans IDE could not recognize the jdk using in freeforms.
Set to higher priority, because developing with this bug is very hard.
reassign to java module for evaluation
Created attachment 49862 [details] Show the Problem: NetBeans default JDK 1.6.2, Maven 2.0 free form, project jdk 1.4, Build OK, IDE shows error
Reassigning to Milos, please evaluate.
by "maven freeform" you mean this? http://mojo.codehaus.org/netbeans-freeform-maven-plugin/ or the maven support modules coming from the netbeans update center? it looks like a duplicate of #104974. Not much we can do in the IDE alone, needs to be first fixed in maven itself. By fix I mean having ways to specify a jdk to be used by the project. Setting source level to 1.4 is not enough.
I mean the maven support modules coming from the netbeans update center. It seems to be a duplicate Bug and because of its complexity it seems that it would not be fixed in the next future. But what could be at least the work around? I would be grateful if I get some tips till the bug is fixed.
marking as duplicate. Please see issue #104974 for a temporary workaround in 6.0 timeframe. *** This issue has been marked as a duplicate of 104974 ***