Community
Participate
Working Groups
While helping Abishek and preparing for a blog I was fighting with class not found errors in the exported product. After investigating I found that a bundle cannot be build because of values in the build.properties file: jre.compilation.profile = J2SE-1.3 javacTarget=jsr14 results in: # 5/31/10 11:50:26 PM CEST # Eclipse Compiler for Java(TM) 0.A54, 3.6.0, Copyright IBM Corp 2000, 2010. All rights reserved. Target level 'jsr14' is incompatible with source level '1.3'. A source level '1.5' or better is required and an empty jar file. Noticed with project: org.eclipse.ecf.remoteservice 4.1.0 The error is only noticable if the project is exported standalone. As part of a product export there is no error only an empty jar which gives you problems at runtime
Created attachment 170596 [details] mylyn/context/zip
I20100520-1744
Hi Wim. I'm looking at this now. I don't use Mylyn so no real need to attach mylyn context. I'm going to remove the jre.compilation.profile from the build.properties for that project (org.eclipse.ecf.remoteservice) and initiate a build. Would you test with the new build, once completed? I'll notify here with the build number when completed.
Removed jre.compilation.profile=J2SE-1.3 from build.properties, and removed J2SE3 from supported execution environments. Released to HEAD. Did rebuild of continuous hudson build for testing. The artifacts for this build are available here: https://ecf2.osuosl.org/hudson/job/C-HEAD-sdk.feature/1065/
This problem appears to occur when the build.properties contains the following: jre.compilation.profile= J2SE-1.3 javacTarget=jsr14 Further, the jdt compiler settings have org.eclipse.jdt.core.compiler.codegen.targetPlatform=jsr14 org.eclipse.jdt.core.compiler.compliance=1.5 The fix described in comment 4 was to simply remove the jre.compilation.profile from the build.properties. Wim should test this fix, and if it solves it for his use case then he should resolve this bug.
Fixed.
