Tom,
Who should we contact for getting this information to the public?
On 12/19/2012 06:22 AM, Tang Yong wrote:
> Hi Siva,
>
>>
>> We can't update weld/core/1.1.10.Final module to incorporate this
>> change, as the module corresponds to the 1.1.0.Final tagged release
>> of Weld, right?
> Yes.
>
>>
>> If this change is critical for users (which I don't think it is), we
>> can integrate Weld 1.1.11.Final (that contains the fix for WELD-1173)
>> into GF trunk.
> I agree with you. Because the change is mainly useful for developer,
> whether we should mention it on some place of glassfish wiki or not?
>
> Thanks
> --Tang
>
>>
>> Thanks
>> --Siva.
>>
>>>
>>> JJ
>>>
>>> On 12/14/2012 04:39 AM, Tang Yong wrote:
>>>> Hi JJ
>>>> CC: Siva, Sahoo
>>>>
>>>> Today, JBOSS Weld Team fixed a bug about weld-osgi-bundle source
>>>> jar[1].
>>>> [1]: https://issues.jboss.org/browse/WELD-1173
>>>>
>>>> I differed the change of bundles/osgi/pom.xml and applied it into my
>>>> local weld 1.1.10.Final based [2].
>>>> [2]:
>>>> https://svn.java.net/svn/glassfish~svn/trunk/external/modules/weld/core/1.1.10.Final
>>>>
>>>>
>>>> After building and confirmation,
>>>> weld-osgi-bundle-1.1.10.Final-sources.jar has been generated
>>>> successfully.
>>>>
>>>> Because fixing version is 1.1.11.Final, I think that until
>>>> 1.1.11.Final
>>>> is released, we can apply it into [2] and this will help CDI developer
>>>> to debug Weld related problems more convenient.
>>>>
>>>> BTW: the attachment is my local bundles/osgi/pom.xml after applying
>>>> fixing.
>>>>
>>>> Thanks
>>>> --Tang
>>
>>
>>
>