[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [p2-dev] Multiple versions of our features
|
That's a good point John, and maybe my use case is not common. But I really want to bind to the latest version, and when I do an update, I want that binding to be updated too. In my case I'm putting together some sample material for EclipseCon, so I want my material to reflect the latest version. I tried not binding to any version of the feature (hoping it would choose the latest on export), but that didn't work.
While my use case may not be common, once we start to provision targets, will this become an issue?
cheers,
ian
2009/3/16 John Arthorne
<John_Arthorne@xxxxxxxxxx>
If you're crafting a product, wouldn't
you want to define and build it against a well-defined target such as an
official release, rather than whatever you happen to be running from week
to week? The question you are trying to answer is whether to define your
product using this week's version of the feature or last week's, but I
would argue the right answer is neither. Instead you should probably define
a target based on an official release, and define your product against
that.
Thanks Pascal,
Yep, I know about the presentation, and this is one side
of it..That bug is referring to an enhancement to improve presentation.
What's happening to me, is I'm actually in a situation where I'm forced
to choose a version. I will raise this there, but I think either
the severity of that bug needs to be raised, or a new bug opened.
cheers,
ian
2009/3/16 Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=263998
Ian
Bull ---03/16/2009 12:08:25 PM---I have been doing week2week upgrades of
the SDK using p2. When I go to craft a product based on fea
I have been doing week2week upgrades of the SDK using p2. When I
go to craft a product based on features, I appear to have multiple versions
of the same feature in my target (multiple versions of the RCP feature
for example). However, the features only differ in the qualifier
(not the human readable part either), so I really am guessing which feature
to install.
Also, if I select the wrong version, export fails.
I think we need a better story around this. Is this something we're
targeting for 3.5? Is it reasonable to only show the latest version of
the feature (possibly with a check box that shows all versions for those
developers fluent in Base 16).
cheers,
ian
--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com
| http://twitter.com/eclipsesource_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com
| http://twitter.com/eclipsesource_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com |
http://twitter.com/eclipsesource