I think we need to warn users of potentials pitfalls doing this.
Just like using a plain jar file as a module is dangerous because jar
files usually do not express well their dependencies (sometimes with
classpath manifest attributes), and usually rely of the environment to
be set correctly (java -cp...).
A module can be used as simple jar file if the environment is set
correctly. however, access to eventual module apis or hk2 services are
of course not guaranteed.
so it takes careful efforts to cross the river each way, although I do
agree that it is doable.
jerome
On Mar 14, 2008, at 11:06 AM, Sahoo wrote:
> What stops a HK2 module jar from being used in a non-HK2 environment?
>
> Thanks,
> Sahoo
>
> 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
>