[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] platform IU ranges in a product definition
Ok, I was trying to understand what you meant by "open the ranges". That is, if you wanted us (Eclipse) to open some ranges (which we can't do for the reasons I said), or if you want to open them in your product.
From a p2 POV, this is doable. p2 doesn't care. However, the tooling seems to be lacking. A quick search through the Eclipse bug DB shows this request .
However, you might be able to simulate this by creating a single feature, and having that feature 'depend' on the features you need. In feature dependencies, you could define the range there.
Hope that helps,
On Thu, Mar 8, 2012 at 12:50 PM, Cortell John-RAT042 <RAT042@xxxxxxxxxxxxx>
I was interested in whether we technically could do what I described, not whether we should. Your first sentence implies we can, but your second expresses
doubt. If not via the product editor, then how/where can these ranges be expressed? I’ve never assembled a product so unfortunately I may be asking a dumb question here. Our product engineering team has told me it’s not possible to specify a range for the
platform IUs. I’m trying to find out if that’s so.
To answer your question, no; it would not be OK if the launchers didn’t match the rest of the platform. The point would be to leave open all the platform
IU ranges (or at least open them somewhat—allow, e.g., a later build of the same major/minor combination). The automated tests would not be run against a random configuration, as the tests will update the platform in its entirety to a specific internal platform
build. Also, the user scenario is not one that is applicable to us.
In your product, feel free to do whatever you wish. I'm not sure if the product editor supports version ranges or not.
However, a few Eclipse components specified ranges for 'include' dependencies a few years ago and this lead to a number of problems. Namely, there is no rhyme or reason to what you will get, that is, you will just get the flavour of the
week. The automated tests will run against some (random) configuration of software, and your users will get another (different) configuration. It all depends what IUs happen to be around at that point in time.
Just in your example below, would it be ok if the launchers didn't match the version of platform? Will that work?
On Thu, Mar 8, 2012 at 6:47 AM, Cortell John-RAT042 <RAT042@xxxxxxxxxxxxx> wrote:
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?
<unit id='com.acme.someproduct' version='1.1.0'>
<update id='com.acme.someproduct' range='0.0.0' severity='0'/>
<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
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
p2-dev mailing list
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484http://eclipsesource.com