I recently wrote about standardizing Eclipse plugins across your team by using a shared Eclipse product extension. We had to do a few things this morning that we hadn’t yet tried since we set this up about a week and a half ago, and it worked out great.

We upgraded our common Subclipse plugin from 0.9.13 to 0.9.16. This turned out to be a really bad idea (not to mention the maintainters are losing my respect), so we backed it out and reverted to 0.9.13. The only thing we had to do was re-enable that plugin on some developers’ Manage Configuration screen (watch out — disabled plugins aren’t shown by default, but you just need to click a button on the toolbar to make them show up again).

We also promoted a plugin from my personal plugin area up to the unstable area. Within 2 or 3 minutes, the move was complete and everyone had the new plugin that wanted to use it. Piece of cake.

We even had a guy move to Eclipse 3.1 M1 last week by simply copying the links folder to his new Eclipse directory as discussed in my other entry. It worked like a charm, and all he was up on 3.1.

So continued experience with this plugin setup seems to be quite favorable. Let me know how you’ve shared or standardized Eclipse plugins in your group.

comments powered by Disqus