On 13 Jun 2014, at 14:28, Nick Boldt wrote:
If it's bad enough we can consider providing a patched version of
an
org.eclipse.* plugin/feature in JBT/JBDS. There is time for that in
Beta3, should it be necessary. We could also put the patch into
Central, like we did for JDK 8 support for Kepler.
once there is a jira actually listing what this bug impacts we can
consider these - but they gotta be serious ones ;)
and no, i don't think the central approach fits this issue. Its not new
piece of functionality.
/max
Nick
On 06/13/2014 07:32 AM, Max Rydahl Andersen wrote:
> before we push too hard the bug should at least have a description on
> what effects it has to users and how to reproduce.
>
> Also, please create jira on our side to track it if its this
> critical.
>
> /max
>
>> Hey Gorkem:
>>
>> Wanted to point you to
>>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351
>>
>> I've currently marked it as a hotbug, but I suspect this isn't
>> correct
>> since technically we have committers on the project (you).
>>
>> If you can assist at pushing this through, I'd be most grateful. I
>> think you're supposed to mark it as p1, since you're a committer.
>>
>> The patch suggestion (adding a synchronized) is safe, and, is
>> clearly
>> the right solution. It's an internal private method, and should in
>> no
>> way NOT be synchronized, so I think this should be an
>> uncontroversial
>> fix for you.
>>
>> Can you do the legwork to get the approvals we need? We're short on
>> time. This race condition is nasty.
>>
>> - Rob
>
>
> /max
>
http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
/max
http://about.me/maxandersen