Community
Participate
Working Groups
Working on big projects like WSAD and eclipse it is easy to get lost in the dependencies of plugins. When you update a plugin to the latest found in CVS it often breaks other plugins. I propose that we add options to perform commands like "update" to act on the selected plugin, and the plugins that it requires. If the plugins that it requires are not checked out, or are present in binary form, it will delete them and check them out in source form. This will make java developing more productive.
>>I propose that we add options to perform commands >>like "update" to act on the selected plugin, and the plugins that it requires This is possible, but if you were in a mixed repository type environment (e.g. some projects under CVS, some under Clearcase) it would only work for the CVS ones. This is because there is no generalized API for loading projects. In the interim you should try Project Sets. They allow you to define a set of projects you want to load. It only does loading, and not mixed "sync some, load the rest" that you seem to be indicating. >>If the plugins that it requires are not checked out, or are present in binary >>form, it will delete them and check them out in source form. I'm not sure how that would work considering we don't know which repositories to find the projects in, and what they may be using as a module alias. Also, I don't think this would be desirable (e.g. are you *sure* you want us to get the latest of say Core or SWT from dev.eclipse.org for you?).
This bug has not been touched in 2 years. Closing as WONTFIX. If you feel this bug is important, feel free to reopen it.
