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.
| Summary: | Javac require non API classes (annotations) in order to compile dependent module | ||
|---|---|---|---|
| Product: | apisupport | Reporter: | Petr Hejl <phejl> |
| Component: | Harness | Assignee: | Jesse Glick <jglick> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
sample project
Test case as suite project |
||
|
Description
Petr Hejl
2008-11-06 17:31:09 UTC
Do you know of a simple way to reproduce this? I created three j2seproject's containing (respectively):
package a;
public @interface A {}
package b;
@a.A
public @interface B {}
package c;
@b.B
public class C {}
I placed A on the classpath of B, and B (but not A) on the classpath of C. C.java then compiled without complaint (using
JDK 6u10).
Looks like there is a problem with enum value. Attaching project that fails. When enum is commented out (and thus sample is reduced to the case you tested) it is compiled without any problem. Created attachment 74083 [details]
sample project
Well your project compiles, but only because it is part of one project. As separate projects, finally I can reproduce:
package a;
public @interface A {
E e();
enum E {V1, V2}
}
package b;
@a.A(e=a.A.E.V1)
public @interface B {}
package c;
@b.B
public class C {}
Added this test case to an existing javac bug report. Created attachment 74095 [details]
Test case as suite project
Working around javac bug in core-main #92fb570474d8. Integrated into 'main-golden', will be available in build *200811250201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/92fb570474d8 User: Jesse Glick <jglick@netbeans.org> Log: #152562: workaround for javac bug 6550655. When an annotation is in a private package, need to at least compile against any enumerations it mentions, or references to a public class using the annotation will abort the compiler. Working around compiler bug by always including enumeration classes in public package JARs, even if they are from private packages. See related issue #157320 about Javadoc execution. You still get e.g.: Compiling 24 source files to .../api.java.classpath/build/classes org/netbeans/api/annotations/common/CheckForNull.class(org/netbeans/api/annotations/common:CheckForNull.class): warning: Cannot find annotation method 'when()' in type 'javax.annotation.Nonnull': class file for javax.annotation.Nonnull not found org/netbeans/api/annotations/common/NonNull.class(org/netbeans/api/annotations/common:NonNull.class): warning: Cannot find annotation method 'when()' in type 'javax.annotation.Nonnull' This is because there are annotations in the CP which are themselved annotated with meta-annotations not in the CP. Fortunately this only seems to cause a warning, not a compiler crash as with the missing enum classes. The only workaround in the Ant harness would be to include annotation classes (as well as enums) in the public package JARs, which seems dangerous - e.g. NB code using @javax.annotation.Nonnull directly would incorrectly compile. Does not affect Maven-based NBM projects, in which compilation uses the original module JARs (ignoring public packages) and the check for invalid impl class dependencies is done separately. |