On Wed, May 28, 2014 at 12:57 AM, Reto Hirt <[email protected]> wrote: > why not simply remove the annotation from the jenkins core and solve that > differently?
If we knew how to solve the (compatibility) issue without this tricky annotation, we would have done so already, I am afraid. > Or should an issue be opened with eclipse? Probably it should, though it would be good for someone to first investigate what the real problem is and whether it can be fixed in the postprocessor associated with the annotation. We are generating bytecode, and perhaps it is invalid, or perhaps it is valid but Eclipse makes certain assumptions that it violates and we would easily work around that. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
