search

wuranjia / jupiter-eclipse-plugin

Automatically exported from code.google.com/p/jupiter-eclipse-plugin
1 stars 6 forks source link

Using the "classic update" in Ganymede causes Jupiter to keep saying a newer version is available #51

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install Jupiter using the classic update in Ganymede
2. Restart Eclipse

What is the expected output? What do you see instead?
The popup that a newer version is available will appear again even though
the new version is in the plugins folder.

For some reason, using the new Ganymede "Software Update" works fine but
the class one doesn't.

Original issue reported on code.google.com by jsakuda on 27 Oct 2008 at 6:38

GoogleCodeExporter commented 9 years ago 
Postponing for 3.4.2 early release.

Original comment by jsakuda on 5 Feb 2009 at 6:49

GoogleCodeExporter commented 9 years ago 
Pulling from milestone to re-evaluate if this feature is still necessary as the 
newer versions of Eclipse have their 
own plugin update system.

Original comment by jsakuda on 28 Jun 2009 at 3:13

GoogleCodeExporter commented 9 years ago 
I think it is time for this feature to go away.  Users can configure their 
Eclipse plugin update system to notify them of out of date plugins.  Will 
remove in release 3.6.1.

Original comment by jsakuda on 22 Jun 2010 at 12:50