Would making HK2 just another Glassfish module solve any issues?
Personally I think having HK2 separate is the wrong way to go, it
makes development difficult, and there are lots of issues with the HK2
stuff.
Lloyd
On Aug 1, 2008, at 6:06 AM, Sahoo wrote:
> Kedar Mhaswade wrote:
>>
>>
>> Sahoo wrote:
>>> Kedar,
>>>
>>> Although right now they can be same, it will be a problem if we
>>> start building HK2 and v3 as part of one maven reactor. So, leave
>>> them as it is.
>>>
>> I don't get it. Please explain why thought of maven reactors change
>> this.
> In the same reactor if the plugin artifacts is built as well
> artifacts depending on the plugin, then it becomes a chicken and egg
> problem, AFAIK. I have not investigated if it is because of the way
> HK2 is organised or a maven behavior.
>
> 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
>