Bug 464756 - ProductCatalogGenerator computes wrong osgi.requiredJavaVersion
Summary: ProductCatalogGenerator computes wrong osgi.requiredJavaVersion
Status: RESOLVED FIXED
Alias: None
Product: Oomph
Classification: Tools
Component: Setup (show other bugs)
Version: 1.1.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eike Stepper CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 346174
Blocks:
  Show dependency tree
 
Reported: 2015-04-16 02:31 EDT by Eike Stepper CLA
Modified: 2015-04-16 02:39 EDT (History)
0 users

See Also:

Attachments
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 Eike Stepper CLA 2015-04-16 02:31:41 EDT 
The ProductCatalogGenerator computes osgi.requiredJavaVersion from p2's touch point instructions, but they don't seem to be specified correctly in all products. As the platform switched to BREE 1.7 for some core bundles (e.g. core.contenttype) the generator needs a work-around until it's clear how to deduce proper values from p2's metadata.
Comment 1 Eike Stepper CLA 2015-04-16 02:35:02 EDT 
The generator is changed and teh catalog regenerated:
http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/commit/?id=d7ce608f235d9070e836cc301172b200d00a1ece
Comment 2 Eike Stepper CLA 2015-04-16 02:39:32 EDT 
The fundamental problem is described here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=346174#c33