| Re: [p2-dev] platform IU ranges in a product definition |
|
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. John From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ian Bull 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? Cheers, Ian 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.
-- |