|p2 install UI wants to reinstall core platform? [message #504657]
||Mon, 21 December 2009 22:30
| Scott Kovatch
Registered: July 2009
We're trying to set up Flex Builder to use p2 for installing new
features. However, the first time I try to install any new feature from
download.eclipse.org I'm told that I need to review and accept the
license agreements on the core features (Eclipse CVS Client, Eclipse
Help System, Eclipse Platform, Eclipse RCP, and Equinox p2
Provisioning), and then it proceeds to "install" all of the bundles
from those features. Then, on the next startup, I see those features as
sub-features of Flash Builder.
Why is p2 doing that? What have we not configured properly such that
the update mechanism knows that those features are already installed?
Now, at this point it gets more interesting. Because our installer
installs Flex Builder into a read-only folder, we want to use the
shared configuration setup using osgi.configuration.cascaded=true. That
appears to be working; on the next launch of Eclipse I see that the
feature I just installed was downloaded to my own configuration
directory. But, if I install another feature, the next launch of
Eclipse will fail because it can no longer find the base features and
plugins folder. I suspect these two things are related, so hopefully
someone can help me figure out the first problem.
I would post a config file or something like that but I don't know
where to start looking.
Thanks in advance,
Flash Catalyst Engineering
Adobe Systems, Inc.
Powered by FUDForum
. Page generated in 0.02876 seconds