Proposal: Put @Native and @GenerateNativeHeader in same package

Paul Benedict pbenedict at
Tue Mar 5 15:38:22 UTC 2013

Okay, but then I think @GenerateNativeHeader should move into lang as well.
Both support tools, both are clear hints (nothing more), and both are
tangentially related to native code. @GenerateNativeHeader has no strict
dependency on anything else in tools package, btw.

On Tue, Mar 5, 2013 at 9:28 AM, Alan Bateman <Alan.Bateman at>wrote:

> On 05/03/2013 15:15, Paul Benedict wrote:
>> :
>> Both are hints for tools. Both discuss header files. So why divide them
>> up?
>> I think they should be in one package together. Personally, I think both
>> are better suited to the package. I just wanted to
>> point out the division doesn't make all that sense.
>>  The reason that @Native was moved from to j.l.annotation is
> because it was problematic for future modularization - ie: it would result
> in a compilation time dependency on the tools module and would also prevent
> its use in the base/core module.
> -Alan.

More information about the core-libs-dev mailing list