|
| Re: Get current version name for 'latest.released' product [message #1737576 is a reply to message #1737575] |
Sun, 10 July 2016 10:55   |
Eclipse User |
|
|
|
Hi Felix,
Comments below...
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 10.07.2016 um 17:17 schrieb Felix Dorner:
> Hi,
>
> In the url attribute of a p2 director task, I need to do something like:
>
> http://download.eclipse.org/sirius/updates/releases/4.0./${scope.product.version.name|lower}
>
> This works when the user initially selects 'Mars' or 'Neon', but not for "Latest (Neon)" or "Latest Released (Neon)".
> Is there a 'filter' or variable that always resolves to the current version name?
No, there's no such filter or variable available.I guess we could add such variables if you open a bugzilla.
>
> Asking more generally, how do I install a given feature from a p2 site whose location depends on the selected product
> version?
Generally these features and their transitive contents *should have* adequate version ranges in their dependencies and
generally, if there are multiple p2 repositories with different such sets of IUs, there also *should be* a composite
repo. So, in an ideal world it should all work by itself :P
|
|
|
| Re: Get current version name for 'latest.released' product [message #1737603 is a reply to message #1737576] |
Mon, 11 July 2016 04:05 |
| Eclipse User |
|
|
|
Hello Eike,
On 10-Jul-16 16:55, Eike Stepper wrote:
>> This works when the user initially selects 'Mars' or 'Neon', but not
>> for "Latest (Neon)" or "Latest Released (Neon)". Is there a 'filter'
>> or variable that always resolves to the current version name?
> No, there's no such filter or variable available.I guess we could add
> such variables if you open a bugzilla.
Ok I'll see.
>> Asking more generally, how do I install a given feature from a p2 site
>> whose location depends on the selected product version?
> Generally these features and their transitive contents *should have*
> adequate version ranges in their dependencies and generally, if there
> are multiple p2 repositories with different such sets of IUs, there also
> *should be* a composite repo. So, in an ideal world it should all work
> by itself :P
>
You mean that if I add both repositories (or one hypothetical composite
one), if the requested feature had proper version ranges the installer
would automatically use the one that matches? (I would really think
that's the way it should work but... I must see to believe.)
In the case of Sirius it's actually a weird one, since their repos
contain exactly the same code, however the mars repo is built against
mars, and the neon repo is built against neon.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03656 seconds
Home