[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] viPlugin disappears after subclipse install

From: jyro <jayeshsalvi_at_gmail.com>
Date: Sat, 9 Feb 2008 11:24:30 -0800 (PST)

I came across the same problem. As Kevin says above, it happens due to the
entry of viplugin in the platform.xml file. From the documentation on the
function of that file, I guess this is what is happening.

The update manager doesn't play nicely with the manually installed plugins
like viPlugin. When one updates or installs plugins like subclipse from
repositories, the platform.xml file is updated. From the
http://help.eclipse.org/stable/topic/org.eclipse.platform.doc.isv/reference/misc/update_platform_xml.html
docs , the "list" and "policy" attributes are used to tag the deprecated
plugin versions as USER-EXCLUDE. When you upgrade a particular plugin - say
org.python.pydev.jython from 1.3.10 to 1.3.13 - then the update manager will
add 1.3.10 to the "list" attribute and set the policy to "USER-EXCLUDE".
Unfortunately, update manager thinks viPlugin is also one of such deprecated
plugins and adds it to the list. >-(

So I removed only the viPlugin related entries from the "list" attribute.
But as Kevin said, even after this and after restart of eclipse the viPlugin
won't show up. &-( Therefore, I deleted all viPlugin files and again
unzipped them. This time restart of eclipse did show all the plugins
including viPlugin.

=)

HTH

-- 
View this message in context: http://www.nabble.com/viPlugin-disappears-after-subclipse-install-tp14695094p15389002.html
Sent from the subclipse - users mailing list archive at Nabble.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-02-09 20:24:41 CET

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.