So, is it OK to move JAXB to glassfish-common (or glassfish-nucleus, if
we need to have it in nucleus distribution, too) package instead of
creating whole new dedicated package?
Jerome Dochez wrote:
> it's me. That sounds like the right solution.
>
> jerome
>
> On Apr 30, 2009, at 1:16 PM, Ed Burns wrote:
>
>>>>>>> On Thu, 30 Apr 2009 13:13:07 -0700, Bhakti Mehta
>>>>>>> <Bhakti.Mehta_at_Sun.COM > said:
>>>>>>
>>
>> BM> Maybe one solution is just remove jaxb from metro package and
>> create a
>> BM> new package for jaxb and let jaxb be available for web
>> distribution?
>>
>> That sounds good. Who is the decider here?
>>
>> Ed
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>