Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369063 - Exporting of stem.product does not work
Summary: Exporting of stem.product does not work
Status: CLOSED FIXED
Alias: None
Product: STEM
Classification: Technology
Component: Core (show other bugs)
Version: 1.3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.1.2   Edit
Assignee: Matthew Davis CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-19 07:10 EST by Christian Thoens CLA
Modified: 2012-01-21 11:16 EST (History)
1 user (show)

See Also:

Attachments
Error log (78.04 KB, application/octet-stream)
2012-01-19 17:00 EST, Christian Thoens CLA 		no flags Details
Built logs (54.78 KB, application/octet-stream)
2012-01-20 09:56 EST, Christian Thoens CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Thoens CLA 2012-01-19 07:10:59 EST 
Exporting stem.products causes the following error:
"Unable to find feature: org.eclipse.equinox.executable"
Adding the Eclipse Delta Pack for 3.6 to the target platform fixes this, but the exported STEM version is not usable. It's possible to create a STEM-project, but when clicking on a button to create a STEM-component (DiseaseModel, PopulationModel, ...) nothing happens.
Comment 1 Matthew Davis CLA 2012-01-19 13:04:18 EST 
Hi Chris,

Do you get a stack trace (in the Error Log) after clicking the buttons?
Comment 2 Christian Thoens CLA 2012-01-19 17:00:08 EST 
Created attachment 209779 [details]
Error log
Comment 3 Christian Thoens CLA 2012-01-19 17:01:18 EST 
Comment on attachment 209779 [details]
Error log

Here is the error log from my home computer (windows 7 64 bit).
Comment 4 Matthew Davis CLA 2012-01-19 17:18:18 EST 
Heh.  That's lovely.

An unresolved compilation error like this should've produced an error log when the Eclipse Product export finished.  Could you check for it and attach too?

I think this is a Java 5/6 compliance issue.  The unresolved compilation error is a @override annotation on an interface method.  I don't think this was supported in Java 5.  Forcing the compiler to use 6 compliance should fix it.

Also could you try adding the following lines to org.eclipse.stem.ui/build.properties then try re-exporting:

javacSource=1.6
javacTarget=1.6

If that doesn't work, in org.eclipse.stem.ui/META-INF/MANIFEST.MF, change the Bundle-RequiredExecutionEnvironment from "J2SE-1.5" to "JavaSE-1.6"
Comment 5 Christian Thoens CLA 2012-01-20 09:56:33 EST 
Created attachment 209826 [details]
Built logs

Hi Matt,

Now it works. I did several things. I have set the Bundle-RequiredExecutionEnvironment to 1.6 and in the project properties I changed the JRE in the build path from 1.5 to 1.6.

I can open the wizards now, but it still says that error occured during the product export. A stack trace is not available, but I attached the build logs.
Comment 6 Matthew Davis CLA 2012-01-20 11:52:57 EST 
Excellent.  Thanks Chris.

Same issue in those logs.

I committed manifest changes for:

org.eclipse.stem.ui.diseasemodels.multipopulation
org.eclipse.stem.ui.foodproduction
org.eclipse.stem.ui.populationmodels
org.eclipse.stem.ui

to change min execution environment from 5 to 6 to reflect the Java 6-specific code in those plugins.

Can you update and try again?  Thanks
Comment 7 Christian Thoens CLA 2012-01-21 09:05:47 EST 
No errors occur anymore.

Thanks Matt