While it is possible to run code during an install, I do not think
many Eclipse plug-ins do it, and Subclipse does not do it. We have
features on an update site. The features are basically just an XML
file that declare the plugins that the feature contains and what
plugins are required to be already be installed. The Eclipse code
does the rest.
Mark
On Tue, Jan 12, 2010 at 10:38 AM, Chris Lott <tigris_at_chris-lott.org> wrote:
> Thanks for the very fast reply. Install and uninstall work fine on many plugins so I am a bit skeptical of looking to the Eclipse platform immediately for relief here. I suspect that the uninstall action is completely determined by the actions of the install action. I think it would be worth checking the Subclipse install configuration to make sure that it's dotting all the Is and crossing all the Ts so the platform knows to do the right thing on removal. However the last time I wrote an eclipse install procedure I was working in version 2. I don't know what all has changed for 3.5, so I don't have anything to offer right now.
>
> ------------------------------------------------------
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2436642
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
>
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2436645
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2010-01-12 16:40:53 CET