Comments on: Building Eclipse plugins with Buildr

By: Antoine Toulme

Antoine Toulme — Fri, 12 Dec 2008 23:35:43 +0000

Eric, would you like to join the effort ?

By: Oisin

Oisin — Fri, 12 Dec 2008 01:21:18 +0000

Excited to see you are taking a go at this, making a complicated eclipse build happen with buildr could be a great way to increase the consumability of Eclipse projects source code

By: Pascal Rapicault

Pascal Rapicault — Thu, 11 Dec 2008 20:09:01 +0000

PDE Build is the right way and should always be preferred because it is in its mandate to support building all the runtime artifacts of eclipse (features, plugins, products, etc.). The releng script is just a layering over PDE that takes care of the complete SDK build and Buckminster also eventually calls PDE / PDE Build.
Consequently recommending people to use other technologies is fine. However potential users have to be made aware that by doing this they are buying out of the evolutions of the build technology that matches the Runtime environment (for example support for Execution Environment, or p2 metadata generation integration, …).

By: Eric Rizzo

Eric Rizzo — Thu, 11 Dec 2008 19:50:28 +0000

There is a huge gaping hole in the community for something that will build update sites headlessly. We’ve spend more than 3 developer-months getting something that works based on PDE Build, but it is hacked together and still does not handle some things well. If you could include Update Site building in your scope, that would be a great benefit to the community.
Also, running plugin tests (JUnit) seems to be a common need; PDE Build sort-of supports it, but not for JUnit4, which is simply ridiculous if you ask me. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=153429

By: Eugene Kuleshov

Eugene Kuleshov — Thu, 11 Dec 2008 16:21:40 +0000

You may also want to look at Tycho. http://blogs.sonatype.com/people/?p=945