The problem has to do with the P2 system used in Eclipse 3.4+. This is the provisioning system, which is responsible for plugin installation and management.
Every so often, P2 performs a "garbage collection" of plugins that are no longer used by Eclipse. If you deliver SDKs by using plugins as the delivery mechanism, P2 deletes the older ones, because Eclipse only runs the latest version of a given plugin. By modifying the plugin ID every time we deliver a new SDK, we prevent P2 from garbage-collecting older SDKs. While this is not an ideal solution, it's a decent compromise until we can come up with another way to deliver SDKs during the Eclipse installation process. On Mon, Feb 8, 2010 at 1:22 PM, Chris Lercher <cl_for_mail...@gmx.net>wrote: > On Feb 5, 4:41 pm, Rajeev Dayal <rda...@google.com> wrote: > > Actually, the problem is that when we release a new SDK, the feature id > > changes, > > I'm curious: Why do you change it? If I understand it correctly, > Eclipse features shouldn't contain the version number as a part of > their feature id. The feature.xml offers a separate 'version' > attribute. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
