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

How to make a framework plugin that does not suck

Max Rydahl Andersen (Red Hat, Inc. )

Making With Eclipse · Standard (25 mins)
Tuesday, 16:15, 25 minutes | Winchester

Tags: Committer And Contributor , Java
7
·
8
·
9
·
10
·
11
·
12
·
13
·
14
·
15
·
16
·
17
·
18

Max Rydahl Andersen

Eclipse plugins that tries to support a specific framework such as Hibernate, JPA, servlets, Struts, Spring, Drools, log4j, etc. all have many of the same challenges but somehow they have a tendency to solve it differently and we end up with a fractured IDE from a usability and architectural perspective.

It seems like everyone understands what functionallity that is specific for their framework, but forget to consider issues like multiple version support, classpath libraries, debugging/launching and coexistence with other 3rd party framework plugins.

After working five years with this in context of JBoss Tools and Eclipse itself I came to realize a lot of this fracture is caused by either not using already existing functionallity available in Eclipse API's or simply not realizing how little effort it actually takes to handle these common issues.

This talk will outline the identified issues and present patterns and in some cases implementation for how framework plugins should be done so they work well within the majority of the Eclipse Java ecosystem.

Max Rydahl Andersen works for Red Hat and is the project lead for JBoss Tools and Developer Studio and is a core developer on Hibernate and Seam.

Max have spoken at several EclipseCon's, JBUG's, JBoss World and Devoxx. Max blogs about JBoss Tools, Eclipse and Hibernate at http://in.relation.to/Bloggers/Max

Slides