Community
Participate
Working Groups
PDE was investigating bug 365661 where an expected API Tools marker was not showing up. Olivier found that the root cause was that the builder and nature were not getting added to the project. The nature is added when a new plug-in project is created and on the second wizard page "Enable API analysis" button is checked. On Windows 7 boxes, using recent builds (I20111201-0855 for me) the nature is never enabled because calling Button.getSelection() always returns false. This is called at org.eclipse.pde.ui PluginContentPage updateData() line 241 data.setEnableAPITooling(fApiAnalysisButton.isVisible() && fApiAnalysisButton.getSelection()); Trying on my Ubuntu box at the office I can't reproduce, but both Michael and Olivier can reproduce on Windows.
Olivier says that while debugging the isVisible() call returns false while getSelection() returns true (correctly). Mike had said getSelection() was causing the problem for him. Mike, can you please confirm. I can't reproduce on my current machine to debug.
Closing as INVALID. The problem is in the PDE wizard itself where we make a call to the button when being on the next page. So in this case, the button is no longer visible. The fix should be done as part of bug 365661.
(In reply to comment #1) > Olivier says that while debugging the isVisible() call returns false while > getSelection() returns true (correctly). > > Mike had said getSelection() was causing the problem for him. Mike, can you > please confirm. When I debugged through, I saw that getSelection was always false and getVisible was always true