Community
Participate
Working Groups
Shouldn't the ability to automatically create an automatic connection to the dev.eclipse.org repository only be in the CVS Repositories context menu if the SDK/PDE function is available? Does not make sense otherwise, and it confuses users of products built on the just the platform. I disabled the SDK/PDE in a build (option still there). I also deleted all feature/plugin dirs associated with PDE/SDK(source) - option still there.
Its a good point. However, PDE isn't CVS specific, so we'ld either need a third plugin just for that, or drop it. Or, some other externalized product level list of favorite places. I agree with your argument that is confusing, so we may just take it out for 2.0.1.
Could the PDE extend an extension point defined in "Team". In a way this is a branding issue, but how many other "brands" are going to provide CVS repositories?
In general the preference is to keep PDE from being CVS specific, since just because you are using PDE doesn't mean you want to connect to eclipse.org. And the opposite is true - I may want to connect to dev.eclipse.org and not use PDE, although that could be considered advanced/rare.
What we'll do for 2.0.1 is remove the action from the menu but keep the action link in the welcome page.
Removed action from Repositories view. Released to R2_0_1.
What does removed from repositories view mean? I used a 2.0.1 build (I0807...) and the option is still there, even when I remove the pde feature/plugin's from the install. I don't see anything in the pde welcome page that suggests that the alternative path is in place.
Verified the fix is in I0812. The fact that we are missing from the welcome page is a separate bug that will be fixed. (21913).
