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.
nbbuild/netbeans/platform/modules/ext/osgi.core-4.3.jar(org/osgi/framework/Bundle.class): warning: [classfile] Signature attribute introduced in version 49.0 class files is ignored in version 48.0 class files core.netigso/test/unit/src/org/netbeans/core/netigso/NetigsoSelfQueryTest.java:462: error: name clash: <S>registerService(Class<S>,S,Dictionary<String,?>) in MockFramework and registerService(Class,Object,Dictionary) in BundleContext have the same erasure, yet neither overrides the other public <S> ServiceRegistration<S> registerService(Class<S> type, S s, Dictionary<String, ?> dctnr) { ^ where S is a type-variable: S extends Object declared in method <S>registerService(Class<S>,S,Dictionary<String,?>) And so on. Except for the period between the fix of bug #208464 and the fix of bug #209239, javac from Ant's JDK is used for compilation, even if nbjdk.home is JDK 6, so this means that you cannot develop Netigso/Netbinox tests from the IDE running on JDK 7 except by running Ant from the CLI. I tried to fix the problems by using raw types. That solved most of the errors, but there was a problem with Comparable vs. Comparable<Bundle> - I could make the sources compile either in JDK 6 or in JDK 7 but not both. Not sure if there is some trick that addresses this. (It is the JDK 6 javac which is buggy.) Is there a version of the OSGi framework JAR available that does not contain malformed class files?
I thought I have already fixed that! Probably the code is laying in some lost local repository. We need to remove the generics from the code.
The other bug was about Netbinox: bug 208666.
#208666 seems to have been about main sources, whereas this is about test sources.
ergonomics#826348ecffb6
Integrated into 'main-golden', will be available in build *201204040400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/826348ecffb6 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #210244: Using raw types, as the generic types in OSGi are not properly defined according to most recent JavaC implementations
Not working for me using 7u4 to compile (6u32 bootcp): core.netigso/test/unit/src/org/netbeans/core/netigso/NetigsoSelfQueryTest.java:200: error: MockFramework is not abstract and does not override abstract method compareTo(Object) in Comparable public static final class MockFramework core.netigso/test/unit/src/org/netbeans/core/netigso/NetigsoSelfQueryTest.java:457: error: method does not override or implement a method from a supertype @Override core.netigso/test/unit/src/org/netbeans/core/netigso/NetigsoSelfQueryTest.java:484: error: MockBundle is not abstract and does not override abstract method compareTo(Object) in Comparable private static final class MockBundle implements Bundle, BundleContent, Comparable<Bundle> { core.netigso/test/unit/src/org/netbeans/core/netigso/NetigsoSelfQueryTest.java:661: error: method does not override or implement a method from a supertype @Override
On my work laptop, I can compile even with JDK1.7.0_04. On my other home laptop, I don't seem to be able to do so. Strange. Probably safer to replace with Proxy...
Remember that the value of nbjdk.home is irrelevant, it is what version of the JDK you run Ant with that counts here. (Unless Ant's JDK is _older_ than nbjdk.home, in which case compilation gets forked.) Using Proxy seems like a good plan, since I think these are all interfaces.
ergonomics#dc7bb5e79da1 - now core.netigso and netbinox tests compile on my computer.
Integrated into 'main-golden', will be available in build *201205230300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/dc7bb5e79da1 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #210244: To eliminate never ending problems with different javac behavior on different JDKs, let us use Proxy for all mock implementations of OSGi interfaces