Gold sponsors

IBM Corporation

SAP

Sonatype

Cisco

JBoss

Intel logo

Oracle

Silver sponsors

bsi logo

Blackberry

Xored

Soyatec

agitar

amazon

Google

Instantiations

Actuate

Microsoft

Bronze sponsors

excelsior

Can't open sponsors/bronze/soyatec/soyatec.

Genuitec

Purple Scout

itemis

Sopera

objectivity

Paremus

froglogic

Activity sponsor

eclipsesource

Media sponsors

TSSJS

SD Times logo

Methods & Tools

GIF89ax-w!,x->;7mmdhI5 zxq}|u{x3tzyt !<wvxvv~~pt~w}u|zsy.~x- |}r/{D;ou/1~ m&]V"c0z2 Kg}Ve&S+,<=j2Msu~Cs~ } YozYVrrx`a.@AEGIzw |W pqq&}zy" ]}'H*\ȰÇD("ŋ3bܨ#ǏC)r"ɓ"S\JMʔs ͙6s܉͟:{ 3M47Atĥ>eiTVJz5+RXvUkUgMRV+wݪsֽ۴ W`z '~;U4HL˘4{B#[~9d^͚ Okm۸sͻ×  )$Iӻ3j"\hνâϾ{_ Ȍ˙'%gyI~G|q~6Zz 'Rև jG@u!^xF NaPAv肎<^@7S/r3 PF)%S,Bẍ$ ė`)f?|Wǘh@"ۑP!Y@vwN $Z.и]zDwp$ZPSv+Tw#Ng;T݉0LN.q%Sy'EK*무9>`p:DQ8]CT8vz,^%,nSZfy5ޙ:Pc,[骥G.:UWz'#_~QRuQO-B&A A&JbUCeRzjƺ1JСr2,0l.zBjkcӞ;+ Iq =s S-2J}p*^ ؙsQM~5״U |dvE1wuղzmUv'HcC-nohݢa7ޞBQ7`# x# @Ӈjx]֛*,WocS[Յ]-j 7!xVB֝f*T< A Ԣ_58Nmdȝfk aL&PiA[ܔǝo}t[Bg ŦEY1ά" ;8a"e>TZV;u]ϵ']j.&7"-t>X6p|>= PMFfoL\ld L$"yHEr,d x*| q$%:sfTVDRh}\W.(ZM7JRgI휪u0|2 l!xt1A,ꀋ)t {WANrhx FCT r,@$z[jIJt X"Vp PBVL},ͨF7ю` XaZTP=Klt!L\ЁNsE ( PJ׳U(`l PrLc]R\`_ á-"DZ7rUZZUNU0Yq \βW2ů_JkW367~倴D;

Be a Sponsor

Get your build configuration in one click with B3 and MoDisco

Henrik Lindberg (Cloudsmith Inc. ), Gabriel BARBIER (Thales Global Services SAS )

Making For Eclipse · Lightning (12 mins)
Monday, 17:02, 13 minutes | Lafayette

Tags: Build and Continuous Integration , Java , Modeling , Tools
7
·
8
·
9
·
10
·
11
·
12
·
13
·
14
·
15
·
16
·
17
·
18

Henrik Lindberg

Gabriel BARBIER

Current software are no longer monolithic, but composed of products, sub-products, etc.. This has induced the need for tools able to build such applications, and to configure continuous integration (nightly build).

These tools may be Eclipse plug-ins like PDE, Buckminster, Athena, B3, etc. But only B3 provides a unique file to define your build process, and the good part is that this file is an EMF model. The not so good is that you have to define your build process manually. And to define your build process easily, you have to discover or express different kind of information. And because it is not so easy, MoDisco project provides some tools to help in discovery process (discoverers definition, composition, execution …). As a use case, several discoverers have been implemented to manage bundles, features (like other tools) and plain old java projects (quiet new) and inject discovered information into B3 models.

Main idea is to repoduce Buckminster entry point : in a few clics, you should be able to build a product packaged like a p2 repository (eclipse update site). But, with added value ! For instance, Buckminster feature is only for eclipse bundles, it could be great to have the same tooling for usual java projects, with external libraries (Maven repository ?), etc..

And the next step is to leverage the learning curve from easy build to custom build. It means a build process independent from the local computer (build server), repeteable and automatic (Hudson configuration) …

 

Link to B3 project

Link to MoDisco project

Henrik is a founder and CTO of Cloudsmith Inc., an Eclipse strategic member and EclipseCon Gold Sponsor(?2010). Henrik has over 20 years of experience architecting and developing innovative infrastructure and application software and tooling. Past positions include leadership of BEA's Java Run-Time Group (JRockit) and CTO and/or technical founder of several publicly and privately held software companies. Henrik leads the Eclipse b3, Eclipse Buckminster and Spaces projects and is a committer on Eclipse p2, and EPP.

Gabriel Barbier works as R&D software engineer for Mia-Software and is committer in Eclipse MoDisco project. He participates also to Modelplex, a research project co-funded by the European Commission to provide Eclipse-based tools to develop complex systems. Before joining Mia-Software, he was a real-time and software engineer at Thales Naval SA where he developped MDA solutions dedicated to component frameworks.