|
Re: shared install and varying configurations [message #50499 is a reply to message #50414] |
Thu, 13 October 2005 07:43 |
Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
Jim,
Great question. The short answer is no, you have to craft a configuration.
Using update.configurator creates a configuration (if one does not exist),
based on the global information that "discovered" in the Eclipse install
area. The update.configurator is promiscuous in this sense.
If you want to have some configurations that include a more limited set of
plugins (and you are using update.configurator) you need to construct a
platform.xml that points the the plugins you want.
Eclipse could use a configuration editor but currently this is largely a
hand rolling effort for you. There is some doc on the platform.xml format
in the help
( http://help.eclipse.org/help31/topic/org.eclipse.platform.do c.isv/reference
/misc/update_platform_xml.html)
Jeff
"Jim VanOosten" <jimvo@us.ibm.com> wrote in message
news:diggpi$emk$1@news.eclipse.org...
> I am using a minimal Eclipse configuration (startup.jar,
> org.eclipse.update.configurator, org.eclipse.core.runtime,
> org.eclipse.core.runtime). I have a single install (osgi.install.area)
> with multiple configuration locations (set via osgi.configuration.area
> property). Currently each configuration location is empty (a
platform.xml
> is not defined), thus all installed bundles can start. I want add some
> bundles that are installed in a different location to one of the
> configurations.
>
> Looking at the configuration support, it appears I have to define a link
to
> the new bundles. Then define a platform.xml for each configuration and
> include the linked bundles only in the configuration that they are needed.
> Is that correct?
>
> Is there a way to include the new bundles with one of the configurations
> without having to define a platform.xml for all of them?
>
> Regards, Jim V.O.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.23894 seconds