Our commercial product's root p2 product metadata specifies a specific build
(XYZ) of various platform IUs for both the bottom and top of the version range
(see below an excerpt from our <number>.profile). I'm being told it's
impossible to open up the version range of these platform IUs. I'm requesting
that the top range be opened up to allow our automated testing scripts to
update the platform (among other things) in a product build via p2 in order to
test that newer version of the platform. I have already determined that this
sort of update is possible by manually opening up the ranges in the .profile
with a text editor.
Is it true that the root product metadata cannot be assembled in a way that has
an open top version range for these platform IUs?
John
<unit id='com.acme.someproduct' version='1.1.0'>
<update id='com.acme.someproduct' range='0.0.0' severity='0'/>
...
<requires size='37'>
<required namespace='org.eclipse.equinox.p2.iu'
name='org.eclipse.equinox.launcher' range='[XYZ,XYZ]'/>
<required namespace='org.eclipse.equinox.p2.iu'
name='org.eclipse.platform.feature.group' range='[XYZ,XYZ]'/>
<required namespace='org.eclipse.equinox.p2.iu'
name='org.eclipse.equinox.launcher.win32.win32.x86' range='[XYZ,XYZ]'>
...
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
