Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: 1. Install the leJOS plug-in (Go to Help -> Software Updates -> Available Software -> Add Site -> http://lejos.sourceforge.net/tools/eclipse/plugin/nxj/) 2. Go to: http://lejos.sourceforge.net/nxj-downloads.php and download and install the software (preferably somewhere handy like C:\ or My Documents). 3. Create a new project (like "mcl"). 4. Right click on the project, go to: leJOS NXJ -> Convert to leJOS NXJ Project. 5. Go to: Project -> Properties -> Java Build Path 6. Click on: Add an External JAR. 7. Navigate to the folder where you installed the leJOS software (step 2) and add \leJOS Projects\pccomms\lib\pccomm.jar 8. Click on Add a Library -> JRE System Library -> Workspace Default. 9. Click OK and return to the project. 10. Create a new package in the src folder (like “computer”). 11. Go to: http://www.cs.uwaterloo.ca/~adcaine/MCL/ 12. Download all of the .java files (except Robot.java). 13. Drag and drop the files into the src folder, but NOT into the new package (files should go into the default package). 14.14. Select all the files in the default package and drag and drop them into the new package. 15. At this point at least one of the files will most likely be sporting the first error. It will complain that: The type Class is not generic; it cannot be parameterized with arguments <T> 16. To see the second error (or if the first is not yet showing), open any file, create and then delete a space, and save the file. It will now exhibit the first error and or complain that it has no idea what object X is, object X being a class who exhibits the first error. More information: I am not sure if the error is being caused by Eclipse or by the leJOS plug-in (I have contacted them, but they are mystified). All I do know is that Eclipse complains that class X is not generic, a thing which I have never heard of before, especially as I am not trying to use any generics.
This has nothing to do with APT. Reassigning to Core. Just a hunch: since it's complaining that Class is not generic, it sounds like a pre-1.5 JRE has been put on the classpath somehow. Perhaps a leJOS classpath container initialization problem, or a race condition in classpath modification (i.e., two threads both trying to getRawClasspath(), modify it, and setRawClasspath() )?
Can you reproduce using 3.5?
For step 8 (8. Click on Add a Library -> JRE System Library -> Workspace Default. ), what JRE System library are you using for the project ?
It seems to work fine with 3.5. I got errors about the NXFInfo constructor being undefined, but no errors like the ones that have been reported. Closing as WORKSFORME.
Verified for 3.6M1
