|Re: [cross-project-issues-dev] Blocking regression in Neon M3 JDT|
To close this thread…
I hit the same issue while working on Sapphire build. This gave me an opportunity to take another look at this issue. After some experimentation, I have determined that what I am hitting appears to be a PDE bug that was exposed by the referenced JDT compiler change in Neon M3.
Basically, the issue is that PDE feature does not require JDT feature. If you start with a base platform and install PDE feature, you get a portion of JDT installed since individual PDE bundles depend on various JDT bundles. This in turns causes PDE Build to invoke JDT compiler in a way that makes it trip on the error documented in Bug 478427.
I have opened a PDE bug.
Two workarounds are available for those affected. Details in the two referenced bugs. Hopefully, this can be fixed for M4.
To further clarify… The bug that I referenced is the one that introduced the regression. Whatever issue it was fixing was a severity “normal”. I reopened the bug when we hit the regression. Let me know if I should open a separate blocking bug instead.
In Neon M3, it’s not a message you can ignore. The build is aborted. See the Git diff in the bug.
I tend to ignore this message. The bug is marked as 'normal' and nothing is indicating that this is blocking something or someone. You should try to be more specific if you send out a note to this list that there is a blocking regression.
Back to the top