| cascaded configurations [message #192391] |
Tue, 06 February 2007 17:55 |
Eclipse User |
|
|
|
Originally posted by: toft.alcatel-lucent.com
I'm new to eclipse and I'm trying to solve a problem where I suspect
that cascaded configurations might be part of a solution, but I've tried
a lot of things, searched the archives on this sight, and googled until
it hurt, and I can't turn up any useful information. So here I post.
The problem or challenge is to support an installation shared by
multiple teams, with specific configurations shared across each team,
plus private configurations for each user. The shared installation would
be basically vanilla with possible "universal" features added, the team
configurations would include team specific feature sets, and the private
configurations would have "my favorite" plugin for users that want this
and are willing to support themselves. I'm not so worried about update
scenarios yet, but I do want to get the basic plumbing working such that
each user gets the correct team features plus their own.
My thought was to provide a wrapper that would call eclipse with
-configuration that pointed to the private location, which would be
seeded with a config.ini that pointed to the team location, which itself
would contain a config.ini that pointed to the installation location.
I've been fiddling with values for osgi.sharedConfiguration.area,
osgi.configuration.area, osgi.sharedConfiguration.area.readOnly, and
osgi.configuration.cascaded, but either I'm barking up the wrong tree or
I haven't hit on the magic combination. I stuck an osgi.splashPath in
the "team" config.ini that's letting me know that I can make that hop,
but the IDE does not come up and I get errors like ...
java.lang.IllegalStateException: Unable to acquire application service.
which sounds like it's not finding the installation's configuration.
Any insight would be appreciated.
Tom
|
|
|
Powered by
FUDForum. Page generated in 0.14435 seconds
Home