Community
Participate
Working Groups
Several b3 projects fail to compile when a 1.5 compliant JVM is installed in Eclipse runtime. The reason for this is that in a strict 1.5 environment, it is not permitted to mark an implemented method with @Override. Only extended method can be marked that way. This was changed in 1.6. The most commonly used JVMs today are 1.6 and above so most people won't notice this (the 1.6 will automatically be used by the build as "1.5 compliant" although that isn't 100% true). The solution for this problem is to do see to that the b3 bundles are compatible with both 1.5 and 1.6. Here are the steps to do that: 1. Open the plug-in manifest editor 2. Add Execlution Environment JavaSE-1.6 3. See to that JavaSE-1.6 is at the top. 4. Save the manifest. 5. Click on "Update the classpath settings" just below the EE window. 6. Open the "build.properties" tab. 7 Add the following line: jre.compilation.profile = J2SE-1.5 8. Save the build.properties file. The last step will ensure that the binaries produced by the build (PDE or Buckminster) can run with a 1.5 VM.
Fixed in trunk for projects o.e.b3: .core .build.* .beelang.* .backend.* This issue was logged for b3.engine, and the bundles listed above are all of the relevant bundles. Please reopen if the intention was to have more bundles fixed.
Reopening for aggregator. It needs to be fixed there as well.
Fixed in rev 1512.
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI. No change to assignee for resolved and verified bugs.]
