Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » P2 » shared bundle pool and features with different versions
shared bundle pool and features with different versions [message #1232723] Fri, 17 January 2014 15:13 Go to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1573
Registered: July 2009
Senior Member
Hi

I've just started playing with eclipse installations with shared
bundlepool (I install them with the p2 director).

Say now that I have two Eclipse SDK installations using the same bundlepool.

I noted that if I install in one eclipse a feature which is already
present in the bundlepool, but with a different version, this version
replaces completely the previous feature (thus invalidating the other
eclipse installation)... I thought that both versions could coexist in
the shared bundlepool... while it is not possible?

I have some ant targets that install different eclipse sdk with the
director (using the bundlepool) and then installs all the features (most
of them are common).
I run one target that installs one eclipse; if I run another ant target
for installing another eclipse installation with basically the same
features as the previous one except for a specific feature with a
different version, as soon as such feature with a different version
replaces the existing one in the bundlepool, then all the other features
(even if they have the same versions of the ones already present in the
bundlepool) are downloaded again...

am I missing something?

thanks in advance
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Re: shared bundle pool and features with different versions [message #1234558 is a reply to message #1232723] Wed, 22 January 2014 08:59 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 5917
Registered: July 2009
Senior Member
Hi Lorenzo,

I think that is because both installations use the same profile in the agent's profile registry. You should create the
installations with different profileIDs. If you don't care about "pretty" profileIDs you could use encoded install
folder paths to help to identify later for what installation a profile was created.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Am 17.01.2014 16:13, schrieb Lorenzo Bettini:
> Hi
>
> I've just started playing with eclipse installations with shared
> bundlepool (I install them with the p2 director).
>
> Say now that I have two Eclipse SDK installations using the same bundlepool.
>
> I noted that if I install in one eclipse a feature which is already
> present in the bundlepool, but with a different version, this version
> replaces completely the previous feature (thus invalidating the other
> eclipse installation)... I thought that both versions could coexist in
> the shared bundlepool... while it is not possible?
>
> I have some ant targets that install different eclipse sdk with the
> director (using the bundlepool) and then installs all the features (most
> of them are common).
> I run one target that installs one eclipse; if I run another ant target
> for installing another eclipse installation with basically the same
> features as the previous one except for a specific feature with a
> different version, as soon as such feature with a different version
> replaces the existing one in the bundlepool, then all the other features
> (even if they have the same versions of the ones already present in the
> bundlepool) are downloaded again...
>
> am I missing something?
>
> thanks in advance
> Lorenzo
>
Re: shared bundle pool and features with different versions [message #1234563 is a reply to message #1234558] Wed, 22 January 2014 09:08 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1573
Registered: July 2009
Senior Member
On 22/01/2014 09:59, Eike Stepper wrote:
> Hi Lorenzo,
>
> I think that is because both installations use the same profile in the
> agent's profile registry. You should create the installations with
> different profileIDs. If you don't care about "pretty" profileIDs you
> could use encoded install folder paths to help to identify later for
> what installation a profile was created.

Thanks Eike!

I was actually using the same profileID; I'll try using different
profileIDs ;)

cheers
Lorenzo

>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
> Am 17.01.2014 16:13, schrieb Lorenzo Bettini:
>> Hi
>>
>> I've just started playing with eclipse installations with shared
>> bundlepool (I install them with the p2 director).
>>
>> Say now that I have two Eclipse SDK installations using the same
>> bundlepool.
>>
>> I noted that if I install in one eclipse a feature which is already
>> present in the bundlepool, but with a different version, this version
>> replaces completely the previous feature (thus invalidating the other
>> eclipse installation)... I thought that both versions could coexist in
>> the shared bundlepool... while it is not possible?
>>
>> I have some ant targets that install different eclipse sdk with the
>> director (using the bundlepool) and then installs all the features (most
>> of them are common).
>> I run one target that installs one eclipse; if I run another ant target
>> for installing another eclipse installation with basically the same
>> features as the previous one except for a specific feature with a
>> different version, as soon as such feature with a different version
>> replaces the existing one in the bundlepool, then all the other features
>> (even if they have the same versions of the ones already present in the
>> bundlepool) are downloaded again...
>>
>> am I missing something?
>>
>> thanks in advance
>> Lorenzo
>>
>


--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Re: shared bundle pool and features with different versions [message #1234653 is a reply to message #1234563] Wed, 22 January 2014 13:40 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1573
Registered: July 2009
Senior Member
Hi Eike

I tried to use two different profileIDs but the problem is still there...

On 22/01/2014 10:08, Lorenzo Bettini wrote:
> On 22/01/2014 09:59, Eike Stepper wrote:
>> Hi Lorenzo,
>>
>> I think that is because both installations use the same profile in the
>> agent's profile registry. You should create the installations with
>> different profileIDs. If you don't care about "pretty" profileIDs you
>> could use encoded install folder paths to help to identify later for
>> what installation a profile was created.
>
> Thanks Eike!
>
> I was actually using the same profileID; I'll try using different
> profileIDs ;)
>
> cheers
> Lorenzo
>
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>>
>>
>> Am 17.01.2014 16:13, schrieb Lorenzo Bettini:
>>> Hi
>>>
>>> I've just started playing with eclipse installations with shared
>>> bundlepool (I install them with the p2 director).
>>>
>>> Say now that I have two Eclipse SDK installations using the same
>>> bundlepool.
>>>
>>> I noted that if I install in one eclipse a feature which is already
>>> present in the bundlepool, but with a different version, this version
>>> replaces completely the previous feature (thus invalidating the other
>>> eclipse installation)... I thought that both versions could coexist in
>>> the shared bundlepool... while it is not possible?
>>>
>>> I have some ant targets that install different eclipse sdk with the
>>> director (using the bundlepool) and then installs all the features (most
>>> of them are common).
>>> I run one target that installs one eclipse; if I run another ant target
>>> for installing another eclipse installation with basically the same
>>> features as the previous one except for a specific feature with a
>>> different version, as soon as such feature with a different version
>>> replaces the existing one in the bundlepool, then all the other features
>>> (even if they have the same versions of the ones already present in the
>>> bundlepool) are downloaded again...
>>>
>>> am I missing something?
>>>
>>> thanks in advance
>>> Lorenzo
>>>
>>
>
>


--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Re: shared bundle pool and features with different versions [message #1234704 is a reply to message #1234653] Wed, 22 January 2014 16:21 Go to previous message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1573
Registered: July 2009
Senior Member
OK, found the problem: I also need to pass the -shared command line
option (possibly with a directory, otherwise it defaults to
${user.home}/.p2).

thanks!
Lorenzo

On 22/01/2014 14:40, Lorenzo Bettini wrote:
> Hi Eike
>
> I tried to use two different profileIDs but the problem is still there...
>
> On 22/01/2014 10:08, Lorenzo Bettini wrote:
>> On 22/01/2014 09:59, Eike Stepper wrote:
>>> Hi Lorenzo,
>>>
>>> I think that is because both installations use the same profile in the
>>> agent's profile registry. You should create the installations with
>>> different profileIDs. If you don't care about "pretty" profileIDs you
>>> could use encoded install folder paths to help to identify later for
>>> what installation a profile was created.
>>
>> Thanks Eike!
>>
>> I was actually using the same profileID; I'll try using different
>> profileIDs ;)
>>
>> cheers
>> Lorenzo
>>
>>>
>>> Cheers
>>> /Eike
>>>
>>> ----
>>> http://www.esc-net.de
>>> http://thegordian.blogspot.com
>>> http://twitter.com/eikestepper
>>>
>>>
>>> Am 17.01.2014 16:13, schrieb Lorenzo Bettini:
>>>> Hi
>>>>
>>>> I've just started playing with eclipse installations with shared
>>>> bundlepool (I install them with the p2 director).
>>>>
>>>> Say now that I have two Eclipse SDK installations using the same
>>>> bundlepool.
>>>>
>>>> I noted that if I install in one eclipse a feature which is already
>>>> present in the bundlepool, but with a different version, this version
>>>> replaces completely the previous feature (thus invalidating the other
>>>> eclipse installation)... I thought that both versions could coexist in
>>>> the shared bundlepool... while it is not possible?
>>>>
>>>> I have some ant targets that install different eclipse sdk with the
>>>> director (using the bundlepool) and then installs all the features (most
>>>> of them are common).
>>>> I run one target that installs one eclipse; if I run another ant target
>>>> for installing another eclipse installation with basically the same
>>>> features as the previous one except for a specific feature with a
>>>> different version, as soon as such feature with a different version
>>>> replaces the existing one in the bundlepool, then all the other features
>>>> (even if they have the same versions of the ones already present in the
>>>> bundlepool) are downloaded again...
>>>>
>>>> am I missing something?
>>>>
>>>> thanks in advance
>>>> Lorenzo
>>>>
>>>
>>
>>
>
>


--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Previous Topic:How to Change Target Path for Downloaded data from P2 repository
Next Topic:Scheduler could not create instance of AutomaticUpdateScheduler > NullPointer
Goto Forum:
  


Current Time: Sat Aug 29 19:11:39 GMT 2015

Powered by FUDForum. Page generated in 0.01692 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software