---
layout: post
title: Salesforce Discusses Its Eclipse Plugin Release Approach
image: >-
  http://kinlane-productions2.s3.amazonaws.com/api-evangelist-site/blog/eclipse-ide-logo.jpeg
author:
  name: kinlane
tags:
  - Plugin
  - Sales
  - Salesforce
---
Salesforce talked a little bit about its [strategy around the development and release strategy around the Salesforce Eclipse plug-in](http://blogs.developerforce.com/developer-relations/2013/02/new-eclipse-plugin-available-february-15th.html).  Providing a little transparency into how they stagger its API releases as well as waiting to release their [Eclipse](http://www.eclipse.org/) plug-in, until API release is complete.

I’m more interested in this story from an [API building block](/buildingblocks/) perspective. An eclipse plug-in seems like a building block for only the most mature APIs out there, and especially ones targeting the enterprise. An eclipse plug-in is not for every API, but I think I will add it as a building block to consider.

It also seems like something a 3rd party provider could step up and find success with as well, by building a single or suite of Eclipse plug-ins that provide integrated API developer tools across popular or high value web APIs for Eclipse users.

I believe IDE plug-ins for APIs will be one way we can provide API discovery solutions for developers, by bringing valuable, qualified API resources into their development environments.