Sahoo wrote:
> What stops a HK2 module jar from being used in a non-HK2 environment?
>
> Thanks,
> Sahoo
>
Sahoo,
I think the basic question is if I delivering some utility code that
- does not use HK-2 facilities, annotations etc.
- provides simple API and implementation to do something,
what is the best way to "package" it -- as a "jar" or "hk2-jar"?
For such a module, what additional benefits would you get by
packaging it as an hk2-jar?
Regards,
Kedar
> Byron Nevins wrote:
>> Yes.
>> So that it can be used by non-hk2 clients as well as hk2-modules.
>>
>>
>> Sahoo wrote:
>>> Byron,
>>>
>>> Have you authored org.glassfish.common:universal module? Why is it
>>> not a HK2 module?
>>>
>>> Thanks,
>>> Sahoo
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>