Haven't found anything on Google or Netbeans forums so far. I'll dig further. I've tried messing around with the manifests (in the build.xml, the '-dl.jar' files don't specify manifest files) with no success yet. Currently seeing if I can duplicate the problem on a Solaris x86 machine.
Thanks, Greg. On Thu, 2011-08-18 at 11:06, Tom Hobbs wrote: > No idea, never seen anything like it before. > > >From what you say it seems like a problem with the class files rather than > the jars. I didn't try anything with any ide when I cut the release > artifacts. Very odd, I assume Google turns up nothing like this in any > netbeans forum or similar? > > > > Grammar and spelling have been sacrificed on the altar of messaging via > mobile device. > > On 18 Aug 2011 16:01, "Greg Trasuk" <[email protected]> wrote: > > Hi folks: > > > > I figured I'd switch the surrogate development over to the newest > > release (2.2.0). I'm using Netbeans (6.9, but moving to 7.0). When I > > pointed the Netbeans project to the new release code, I saw red. As in, > > many red squiggly lines. Netbeans appears unable to read the jar files > > for 'jsk-platform.jar', 'jsk-lib.jar' or 'jsk-resources.jar'. > > > > To be completely accurate, Netbeans is able to see the '.class' files > > inside the jar files, but can't read the class definitions, so it can't > > enumerate the methods and fields, so it can't do auto-import or > > auto-completion. The project builds fine, so it appears the jar files > > are readable by 'javac'. > > > > Oddly, Netbeans _is_ able to read the 'jsk-dl.jar' classes properly. In > > fact, the same holds for all the '-dl' files. Can't read 'reggie.jar', > > but reads 'reggie-dl.jar' just fine. > > > > I get the same results if I check out the River trunk and build from > > source. > > > > I've tried Netbeans 6.8, 6.9, and 7.0 with the same results. Haven't > > tried Eclipse yet. > > > > Does anyone have any ideas before I jump into the River build to see > > what might be happening? > > > > Cheers, > > > > Greg. > > > >
