Geek Answers Handbook

Continuous integration and development of the eclipse plugin

I am developing a set of eclipse plugins, and I have several JUnit plugin tests that actually run another eclipse instance, create a workspace layout and a project layout and perform various operations on them. I want to say that on constant integration, and I am at a loss as to where to start. I am using Hudson, will there be any plugins that simplify this? Can these tests trigger an eclipse headless or something on a CI server? Pointers will be highly appreciated.

+5
source share
3 answers

I think the best solution for creating Eclipse-based software at the moment is Tycho - it is based on Maven and uses your standard Eclipse files (e.g. manifest, target platform, product definition). I started with him, using the introduction of this blog: http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/ , and it worked very well. We also use Hudson, and since Tycho is Maven-based, Hudson integration was trivial and worked just by calling Maven, which Hudson supports out of the box.

+2
source

, Buckminster : , Buckminster .

, Buckminster.

+1

Maybe this will help you avoid plugins ?;) I like to avoid them ... using the object layout ...

http://blog.srvme.de/2010/12/10/mock-eclipse-ifile/

0
source

More articles:


All Articles