Community
Participate
Working Groups
I'm opening this bug to track the compile error in wtp-R3.2.0-I/20091022044124 since those committers are not immediately available to fix it.
Since the responsible committers are not immediately available, I was considering just commenting out the offending code, with would of course will not work, and just remove the compile error. But ... I've checked, and the bundle is still produced. If someone tried to use that particular code, they'd get an error of course, BUT ... in this case I don't think anyone is using this code yet (its new) and since builds take at least 6 or 7 hours these days, I don't think its a good use of build time just to make a red x disappear. So ... we'll declare even though we have a compile error. For the record, this was related to a change in last week's JEE code, but the committer apparently was using an older target, so didn't notice the change. Valintine investigated (thanks Valintine) and said, <quote> ... from talking to Jason, the JavaEE folks appear to have made their models type safe (using Java generics) sometime at the end of last week, and this change is exposing a bug in the JAX-RS facet code. </quote>
How soon will this be fixed? 20091027011548 was still broken.
Changing to blocker. (Normally it would have been blocker last week ... but, that was an exception). We won't declare another build without it! (If that's not obvious). Thank you for quick attention.
Fix released for the next build.
