I do not think it is possible for the installation of a plugin to
alter that file. We certainly do not do anything other than package
our plugin as a standard feature. Eclipse does all the work of
editing its internal files. That being said, if someone determines
that changing something about the Subclipse packaging would prevent
the problem I would certainly be willing to look into it.
Mark
On Jan 8, 2008 12:49 PM, Kevin Tomasek <ktomasek_at_d2audio.com> wrote:
>
> this seems to happen often (if you read the viPlugin pages)
>
> the solution to the problem is as follows (snipped from viPlugin pages)
>
>
>
> -----------QUOTE ---------
> I had to manually edit the platform.xml file....
> It had this entry in it:
>
> Somehow, ViPlugin got in that list of things that had a "USER-EXCLUDE"
> policy....Perhaps it happened when epic was installed, or when I disabled
> it....who knows....
>
> But I removed the viplugin entry from that list, and I got my plugin
> back....
> ------------ENDQUOTE -----------------
>
> the platform.xml is located at /configuration/org.eclipse.update
>
> removing the viPlugin info from the 'list= " ' section did nothing. for me
> that left an empty double quotes 'list=""'. once i deleted the line
> entirely, the plugin was once again visible.
>
> hopefully, this will save the next guy some time..
>
>
> i don't know if it an eclipse problem or a subclipse problem. i don't know
> who or what causes the platform.xml file to get modified.
>
>
> ideas??
>
>
>
>
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-01-08 18:57:10 CET