http://www.ralfebert.de/blog/eclipsercp/rcp_builds/

One drawback in my experience is that the learning curve for Buckminster is pretty steep.

Good to hear from you! I don’t know of any easier way to create a target platform than the one you describe. But downloading and zipping the file isn’t too difficult! You then will need to add at least the JUnit plug-in if you want to do unit testing.

As for sharing it, I’d definitely consider placing the platform on a shared drive. It’s also nice to have a wiki page listing the plug-ins needed for each application. And versioning the target platform is a *great* idea.

I’m actually preparing a post on target platform best-practices for next week, so keep watching for that.

— Patrick

Thanks for this post. It could not have come at a better time.

I am currently working on an RCP Application with a team of developers. We are in the initial stages when we happened upon your blog post. I am convinced that the creation of a target platform is critical to the life of an RCP Application.

Now that we have that established, I was wondering if you knew of a good way to create an initial target platform. I went ahead and manually a folder and placed all of the necessary RCP Binaries into that folder. I was hoping that there would be a way to do this more automatically, but I could not find anything.

Also, what is the best way to share the target platform with other developers. One of the main reasons why I put the plugins manually into a seperate folder is so that we can then version control the Target Platform in Subversion.

Is there a better approach for the above two methods?

Thanks in advance for your response.

Carlus