Eclipse Community Forums: Oomph » Enabling shared bundle pool in standalone installations

Help

Home

Home » Eclipse Projects » Oomph » Enabling shared bundle pool in standalone installations

Show: Today's Messages :: Show Polls :: Message Navigator

Enabling shared bundle pool in standalone installations [message #1796052]

Thu, 04 October 2018 13:37

Tim Sibirsky

Messages: 9
Registered: October 2018

Junior Member

Hello!

Let's assume that I have an instance of Eclipse product that: a) was installed with Oomph, but without using shared bundle pool; b) was simply downloaded as an archive, so it was installed without Oomph mechanisms.

Is it possible to "enable" shared bundle pool for this instance later, in both cases? For example, maybe, move existing plugins and features of this instance to bundle pool (or simply install them again, but into the bundle pool) and reconfigure instance to use bundle pool?

And another question: is it possible to "bind" Eclipse product instance that was installed without Oomph mechanisms (as described in first question) with any product in remote Oomph catalog?

Thanks for answers!

Report message to a moderator

Re: Enabling shared bundle pool in standalone installations [message #1796438 is a reply to message #1796052]

Fri, 12 October 2018 23:02

Ed Merks

Messages: 30908
Registered: July 2009

Senior Member

No, the whole layout of such an installation is totally different and can't be converted.

If you use Navigate -> Open Setup -> Installation you can use the properties view on the root Installation object in that resource to "link" it to a Product Version from the catalog. If you then do Help -> Perform Setup Tasks, the installation will update to try to match that Product Version.

Report message to a moderator