This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Hi, Over the past months we've been adding OS/2-specific tweaks to make Netbeans run on OS/2 using IBM's JDK. Recently, there 3rd-party support has been added for Sun JDK 1.4.1 ported to OS/2. What we need to do now is scan the entire Netbeans code for OS/2-specific patches and verify that they still make sense. Specifically, I know there are some patches out there that are invoked if OS/2 is detected but they are really meant to work against IBM's JDK. We need to reclassify these fixes against IBM's JDK, OS/2 or both of them together; otherwise I forsee a whole new slew of bug reports when people start using Sun's JDK under OS/2. Scanning for this should be rather easy. I believe you have some sort of constant for OS/2-specific patches. Can we scan for it? Thanks, Gili
David K. was playing with PMD. He is probably able to answer this question.
PMD is not relevant to this. I asked around and guys doing some OS2 specific changes do not remember adding any special tags to source code. Still it might worth to ask on nbdev. There exist constant org.openide.util.Utilities.OS_OS2 which could be grepped for, but I do not know how successfull it will be. I would try to also search for all fixed issues filed for OS2 OS and ask the guy who fixed it. I do not know what to do with this task now, but it is not defect. It can be TASK, but I'm not sure who should work on it.
Yours to drive I guess...
Added dependency on issue 34124. We're fairly close (85%) to getting identical behavior under OS/2 and Windows.
Marking UMBRELLA under the assumption that specific problems found + patched will be filed as separate issues given in the dependency list of this issue.
I'm actually no longer the official Netbeans under OS/2 supporter. Unless someone else is willing to drive this issue, please close as WON'T FIX. Sorry :(
OK, waiting for an owner.
Closing as suggested.
This issue was solved long time ago. Because nobody has reopened it neither added comments, we are verifying/closing it now. If you are still able to reproduce the problem, please reopen. Thanks in advance.