Hi Mark,
Mark Phippard wrote:
>
>
> First off, I am willing to do whatever it takes. So let's just figure
> out what the right thing to do is.
>
> If I made a headless feature, wouldn't you still have a problem if
> someone had the normal feature installed? I guess it depends on
> whether you require the feature or the core plugin.
>
I'm not sure but I think the Eclipse Update Manager handles that for us
so that installing the headless feature would become a no-op. I don't
see it as a problem regardless.
> What I would probably do is make a "headless" update site where that
> feature was located, so that "normal" users are not confused about
> what to install. Would that be OK with you?
>
Yes, that's OK. What I'm after is the level of indirection that the
feature will give us so that nothing breaks when you publish new bugfix
versions. We are not sensitive to the exact URL of the update site as
long at it stays the same.
> What do you do with CVS? AFAIK, Eclipse does not provide multiple
> ways to install their stuff.
>
Well, that's not pretty either to be honest, and it's not just CVS, but
all headless plugins that we need from Eclipse. At present we must
maintain our own feature for that and it appoints exact versions of the
needed Eclipse bundles. This is not too bad for us though since we
monitor the Eclipse releases very closely for other reasons.
Kind Regards,
Thomas Hallgren
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Thu Jan 25 17:21:16 2007