Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315149

Summary: [releng] build.properties values causes export problem
Product: [RT] ECF Reporter: Wim Jongman <wim.jongman>
Component: ecf.relengAssignee: Scott Lewis <slewis>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: P3 CC: bugs.eclipse.org, slewis
Version: unspecified   
Target Milestone: 3.3.0   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
mylyn/context/zip none

Description Wim Jongman CLA 2010-05-31 18:30:52 EDT 
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
Comment 1 Wim Jongman CLA 2010-05-31 18:32:07 EDT 
Created attachment 170596 [details]
mylyn/context/zip
Comment 2 Wim Jongman CLA 2010-05-31 18:34:05 EDT 
I20100520-1744
Comment 3 Scott Lewis CLA 2010-05-31 18:44:27 EDT 
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.
Comment 4 Scott Lewis CLA 2010-05-31 19:45:54 EDT 
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/
Comment 5 Scott Lewis CLA 2010-06-01 09:27:18 EDT 
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.
Comment 6 Scott Lewis CLA 2010-06-06 20:49:50 EDT 
Fixed.