On 12/2/2015 11:44 AM, Alex Buckley wrote:
On 12/2/2015 2:16 AM, Stephane Epardaud wrote:
On 01/12/15 22:04, Alex Buckley wrote:
There shouldn't be any surprise here. In Java SE 8, you can declare a
package-private annotation type and use it to write annotations on
public classes of that packag
On 12/2/2015 2:16 AM, Stephane Epardaud wrote:
On 01/12/15 22:04, Alex Buckley wrote:
There shouldn't be any surprise here. In Java SE 8, you can declare a
package-private annotation type and use it to write annotations on
public classes of that package. Going up a level in Java SE 9, you can
de
On 01/12/15 22:04, Alex Buckley wrote:
> There shouldn't be any surprise here. In Java SE 8, you can declare a
> package-private annotation type and use it to write annotations on
> public classes of that package. Going up a level in Java SE 9, you can
> declare a module-private annotation type (
On 12/1/2015 7:47 AM, Stephane Epardaud wrote:
I'm using reflection to walk classes and methods, and walking
java.lang.Object.hashCode() I get an annotation of type
jdk.internal.HotSpotIntrinsicCandidate, which does not appear to be
exported by java.base (it exports jdk but not jdk.internal). Is
On 01/12/2015 15:47, Stephane Epardaud wrote:
Hi,
I'm using reflection to walk classes and methods, and walking
java.lang.Object.hashCode() I get an annotation of type
jdk.internal.HotSpotIntrinsicCandidate, which does not appear to be
exported by java.base (it exports jdk but not jdk.internal).
Hi,
I'm using reflection to walk classes and methods, and walking
java.lang.Object.hashCode() I get an annotation of type
jdk.internal.HotSpotIntrinsicCandidate, which does not appear to be
exported by java.base (it exports jdk but not jdk.internal). Is that
intentional? I would have thought that
