Luca Morettoni wrote:
> On 01/29/10 01:09 AM, glassfish_at_javadesktop.org wrote:
>
>> This seems to be a change introduced in Java 6u18. Our quality team
>> and compatibility test team are also now seeing this. I've also
>> reproduced this on a Windows system with 6u18 installed.
>>
>> As I mentioned earlier in this thread, I added a workaround to
>> GlassFish several days ago. I have also opened a GlassFish issue
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=11494 for this
>> because I suspect we will want to include that workaround in the
>> proposed next update release to GlassFish 3.0.
>
>
>
>
> Thanks Tim, do you know when the 3.0.1 version could be available into
> pkg repository? And in witch repository too... :)
>
The issue note says that the workaround made it into the 3.0.1 branch on
02/04. We are promoting 3.0.1 branch build later today, so look for
packages with the version 3.0.1,0-4 in the dev.glassfish.org repository.
Note that you will need to use the procedure described in this thread to
see the update since we are not updating stable.glassfish.org repository
just yet so this will not be automatically handled as image update:
http://forums.java.net/jive/thread.jspa?messageID=382872
Thanks,
Snjezana