Max Andersen, profile picture
Uploaded byMax Andersen
1,603 views

Tycho - good, bad or ugly ?

The document discusses Max Rydahl Andersen's presentation at EclipseCon 2012 regarding Tycho, a project focused on plugins for JBoss and related technologies within the Eclipse Marketplace. It highlights the project's structure, including numerous plugins, modules, and features, as well as the Tycho versioning system for managing plugin updates and dependencies. The content emphasizes the significant scale and complexity of the Tycho project, incorporating various development and testing elements.

Embed presentation

Tycho: Max Rydahl Andersen Red Hat at EclipseCon 2012
Tycho: Max Rydahl Andersen Red Hat at EclipseCon 2012
•Plugins for JBoss and related technology •AS, JSF, CDI, Seam, Portal, Birt, Maven, … •Top ~5 plugin on Eclipse Market Place
1.200.000 starts of JBoss Tools January-March 2012
•45 modules •~8 year old •222 plugins •PDE Ant Build •76 features •36 test features •154 test plugins
•45 modules •~8 year old •222 plugins •PDE Ant Build •76 features •36 test features •154 test plugins a.k.a. The “Big Ass” Project that moved to Tycho
PDE/Ant Build common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
PDE/Tycho common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
PDE/Tycho common plugins .core <?xml version="1.0" encoding="UTF-8"?> <project> <modelVersion>4.0.0</modelVersion> .ui <parent> <groupId>org.jboss.tools.common</groupId> ... <artifactId>plugins</artifactId> <version>3.3.0-SNAPSHOT</version> </parent> features .feature <groupId>org.jboss.tools.common.plugins</groupId> .source.fe <artifactId>org.jboss.tools.common</artifactId> ature <packaging>eclipse-plugin</packaging> </project> ... tests .tests ... site
PDE/Tycho common plugins .core <?xml version="1.0" encoding="UTF-8"?> <project> <modelVersion>4.0.0</modelVersion> .ui <parent> <groupId>org.jboss.tools.common</groupId> ... <artifactId>plugins</artifactId> <version>3.3.0-SNAPSHOT</version> </parent> features .feature <groupId>org.jboss.tools.common.plugins</groupId> .source.fe <artifactId>org.jboss.tools.common</artifactId> ature <packaging>eclipse-plugin</packaging> </project> ... <packaging>eclipse-test-plugin</packaging> <packaging>eclipse-feature</packaging> tests .tests <packaging>eclipse-repository</packaging> <packaging>eclipse-application</packaging> ... site
common plugins .core ”Big Ass” .ui ... features .feature .source.fe ature ... tests .tests ... site
common plugins .core hibernate CDI ”Big Ass” plugins .core JSF plugins .core ... plugins .core ... plugins .core plugins .core seam plugins .core .ui .ui .ui .ui .ui .ui .ui ... ... ... ... ... features .feature ... ... .source.fe features .feature features .feature ature features .feature features .feature features .feature features .feature ... .source.fe ature .source.fe ature .source.fe .source.fe .source.fe tests .tests .source.fe ature ature ature ... ature ... ... ... ... ... tests .tests site ... tests .tests ... tests .tests tests .tests tests .tests tests .tests ... site ... site ... ... ... site site site site ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui ... ... ... ... ... ... ... ... ... ... ... ... features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe ature ature ature ature ature ature ature ature ature ature ature ature ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... ... ... ... ... ... ... ... ... ... ... ... .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature site site site site site site site site site site site site .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe ature ature ature ature ature ature ature ature ature ature ature ature ... ... ... ... ... ... ... ... ... ... ... ... tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... ... ... ... ... ... ... ... ... ... ... ... .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui site site site site site site site site site site site site ... ... ... ... ... ... ... ... ... ... ... ... features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe ature ature ature ature ature ature ature ature ature ature ature ature ... ... ... ... ... ... ... ... ... ... ... ... tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests ... ... ... ... ... ... ... ... ... ... ... ... site site site site site site site site site site site site
General Layout common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
General Layout common plugins .core •module is a “releasable unit” .ui ... features .feature .source.fe ature ... tests .tests ... site
General Layout common plugins .core •module is a “releasable unit” .ui •pom.xml at each level ... features .feature .source.fe ature ... tests .tests ... site
General Layout common plugins .core •module is a “releasable unit” .ui •pom.xml at each level ... •allows to build subparts very features .feature easily .source.fe ature ... tests .tests ... site
General Layout common plugins .core •module is a “releasable unit” .ui •pom.xml at each level ... •allows to build subparts very features .feature easily .source.fe •separate customization for ature modules ... tests .tests ... site
General Layout common plugins .core •module is a “releasable unit” .ui •pom.xml at each level ... •allows to build subparts very features .feature easily .source.fe •separate customization for ature modules •Can use mvn version per module ... tests .tests ... site
tycho-versions-plugin common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
tycho-versions-plugin common plugins .core 1.0.2 2.0.1 2.0.1 .ui 1.0.3 ... 1.1.2 features .feature 2.0.1 2.0.1 .source.fe ature 2.0.1 ... 1.1.2 tests .tests 1.1.2 2.0.1 ... 1.1.2 site 1.1.3
tycho-versions-plugin common plugins .core 1.0.2 2.0.1 2.0.1 .ui 1.0.3 ... 1.1.2 mvn org.eclipse.tycho:tycho-versions- features .feature 2.0.1 plugin:set-version -DnewVersion=2.0.2 2.0.1 .source.fe ature 2.0.1 ... 1.1.2 tests .tests 1.1.2 2.0.1 ... 1.1.2 site 1.1.3
tycho-versions-plugin common plugins .core 1.0.2 2.0.2 2.0.2 .ui 1.0.3 ... 1.1.2 features .feature 2.0.2 2.0.2 .source.fe ature 2.0.2 ... 1.1.2 tests .tests 1.1.2 2.0.2 ... 1.1.2 site 1.1.3
tycho-versions-plugin common plugins .core 2.0.2 2.0.2 2.0.2 .ui 2.0.2 ... 2.0.2 features .feature 2.0.2 2.0.2 .source.fe ature 2.0.2 ... 2.0.2 tests .tests 2.0.2 2.0.2 ... 2.0.2 site 2.0.2
tycho-versions-plugin common plugins .core 2.0.2 2.0.2 2.0.2 .ui 2.0.2 ... 2.0.2 mvn org.eclipse.tycho:tycho-versions- features .feature 2.0.2 plugin:set-version -DnewVersion=2.1.0 2.0.2 .source.fe ature 2.0.2 ... 2.0.2 tests .tests 2.0.2 2.0.2 ... 2.0.2 site 2.0.2
tycho-versions-plugin common plugins .core 2.1.0 2.1.0 2.1.0 .ui 2.1.0 ... 2.1.0 features .feature 2.1.0 2.1.0 .source.fe ature 2.1.0 ... 2.1.0 tests .tests 2.1.0 2.1.0 ... 2.1.0 site 2.1.0
tycho-versions-plugin common plugins .core 1.7.3 2.1.0 2.1.0 .ui 2.1.0 ... 2.1.0 features .feature 2.1.0 2.1.0 .source.fe ature 2.1.0 ... 2.1.0 tests .tests 2.1.0 2.1.0 ... 2.1.0 site 2.1.0
tycho-versions-plugin common plugins .core 1.7.3 2.1.0 2.1.0 .ui 2.1.0 ... 2.1.0 mvn org.eclipse.tycho:tycho-versions- features .feature 2.1.0 plugin:set-version -DnewVersion=2.1.1 2.1.0 .source.fe ature 2.1.0 ... 2.1.0 tests .tests 2.1.0 2.1.0 ... 2.1.0 site 2.1.0
tycho-versions-plugin common plugins .core 1.7.3 2.1.1 2.1.1 .ui 2.1.1 ... 2.1.1 features .feature 2.1.1 2.1.1 .source.fe ature 2.1.1 ... 2.1.1 tests .tests 2.1.1 2.1.1 ... 2.1.1 site 2.1.1
tycho-versions-plugin common plugins .core 1.7.3 2.1.1 2.1.1 .ui 2.1.1 •Easy update of versions in ... 2.1.1 •pom.xml •manifest.mf features .feature 2.1.1 •feature.xml 2.1.1 .source.fe ature 2.1.1 •site.xml ... 2.1.1 •.product tests .tests 2.1.1 •…. 2.1.1 ... 2.1.1 •Don’t Repeat Yourself site 2.1.1
Plugin A Require-Bundle: Z [1.2;2.0] Plugin B Plugin C Require-Bundle: Z [1.7;2.0] Source
Plugin A Require-Bundle: Z [1.2;2.0] Plugin B Plugin C Require-Bundle: Z [1.7;2.0] Source ~/.m2/repository
Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Q 1.2.1 Plugin B Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source ~/.m2/repository
Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Q 1.2.1 Plugin B Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin Z 1.8 ~/.m2/repository
Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Q 1.2.1 Plugin B Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin B 1.2.3 Plugin C Plugin Z 1.8 1.2.3 Plugin A 1.2.3 ~/.m2/repository
Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source ~/.m2/repository
Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin Z 1.7 Plugin Q 1.2.1 ~/.m2/repository
Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin C 1.2.3 Plugin A Plugin Q 1.2.1 1.2.3 ~/.m2/repository
Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin C 1.2.3 Plugin A Plugin Q 1.2.1 1.2.3 ~/.m2/repository
Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin C Plugin B 1.2.3 1.2.3 Plugin A Plugin Q 1.2.1 1.2.3 Plugin A 1.2.3 ~/.m2/repository
p2 repositories Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin C Target Definition Plugin Z 1.7 Require-Bundle: Z Plugin Z 1.8 [1.7;2.0] B Plugin Z 2.0 Source Plugin B 1.2.3 Plugin A 1.2.3 ~/.m2/repository
p2 repositories Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin C Target Definition Plugin Z 1.7 Require-Bundle: Z Plugin Z 1.8 [1.7;2.0] B Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin B 1.2.3 Plugin Q 1.2.1 Plugin A 1.2.3 ~/.m2/repository
p2 repositories Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin C Target Definition Plugin Z 1.7 Require-Bundle: Z Plugin Z 1.8 [1.7;2.0] B Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin B 1.2.3 Plugin C Plugin Q 1.2.1 1.2.3 Plugin A 1.2.3 ~/.m2/repository
! ! <format>'v'yyyyMMdd-HHmm'-${BID}'</format>
! ! <format>'v'yyyyMMdd-HHmm'-${BID}'</format>
! ! <format>'v'yyyyMMdd-HHmm'-${BID}'</format>
! ! <format>'v'yyyyMMdd-HHmm'-${BID}'</format>
! ! <format>'v'yyyyMMdd-HHmm'-${BID}'</format>
! ! <format>'v'yyyyMMdd-HHmm'-${BID}'</format>
0.13+ ! ! <format>'v'yyyyMMdd-HHmm'-${BID}'</format>
Update Sites common plugins .core artifacts.jar content.jar .ui features/org.jboss.tools.forge.feature_1.0.0.v20120327-0403-Beta3.jar ... features/org.jboss.tools.forge.test.feature_1.0.0.v20120327-0403-Beta3.jar features .feature .source.fe plugins/org.jboss.tools.forge.core.test_1.0.0.v20120327-0403-Beta3.jar ature plugins/org.jboss.tools.forge.core_1.0.0.v20120327-0403-Beta3.jar ... plugins/org.jboss.tools.forge.runtime.ext_1.0.0.v20120327-0403-Beta3.jar tests .tests plugins/org.jboss.tools.forge.runtime_1.0.0.v20120327-0403-Beta3.jar ... site plugins/org.jboss.tools.forge.ui.test_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.ui_1.0.0.v20120327-0403-Beta3.jar
Source Features common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
Source Features <plugins> common plugins .core <plugin> <groupId>org.eclipse.tycho.extras</groupId> <artifactId>tycho-source-feature-plugin</artifactId> .ui <version>${tychoVersion}</version> <executions> <execution> ... <id>source-feature</id> <phase>package</phase> <goals> features .feature <goal>source-feature</goal> </goals> </execution> .source.fe </executions> ature </plugin> <plugin> ... <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-p2-plugin</artifactId> <version>${tychoVersion}</version> tests .tests <executions> <execution> <id>attached-p2-metadata</id> <phase>package</phase> ... <goals> <goal>p2-metadata</goal> site </goals> </execution> </executions> </plugin> </plugins>
Source Features <plugins> common plugins .core <plugin> <groupId>org.eclipse.tycho.extras</groupId> <artifactId>tycho-source-feature-plugin</artifactId> .ui <version>${tychoVersion}</version> <executions> <execution> ... <id>source-feature</id> <phase>package</phase> <goals> features .feature <goal>source-feature</goal> </goals> </execution> .source.fe </executions> ature </plugin> <plugin> ... <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-p2-plugin</artifactId> <version>${tychoVersion}</version> tests .tests <executions> <execution> <id>attached-p2-metadata</id> <phase>package</phase> ... <goals> <goal>p2-metadata</goal> site </goals> </execution> 0.14+ </executions> </plugin> </plugins>
Source Features <plugins> common plugins .core <plugin> <groupId>org.eclipse.tycho.extras</groupId> <artifactId>tycho-source-feature-plugin</artifactId> .ui <version>${tychoVersion}</version> <executions> <execution> ... <id>source-feature</id> <phase>package</phase> <goals> features .feature <goal>source-feature</goal> </goals> </execution> .source.fe </executions> ature </plugin> <plugin> ... <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-p2-plugin</artifactId> <version>${tychoVersion}</version> tests .tests <executions> <execution> <id>attached-p2-metadata</id> <phase>package</phase> ... <goals> <goal>p2-metadata</goal> site </goals> </execution> </executions> </plugin> </plugins>
Source Features common plugins .core artifacts.jar content.jar .ui features/org.jboss.tools.forge.feature_1.0.0.v20120327-0403-Beta3.jar ... features/org.jboss.tools.forge.test.feature_1.0.0.v20120327-0403-Beta3.jar features .feature .source.fe plugins/org.jboss.tools.forge.core.test_1.0.0.v20120327-0403-Beta3.jar ature plugins/org.jboss.tools.forge.core_1.0.0.v20120327-0403-Beta3.jar ... plugins/org.jboss.tools.forge.runtime.ext_1.0.0.v20120327-0403-Beta3.jar tests .tests plugins/org.jboss.tools.forge.runtime_1.0.0.v20120327-0403-Beta3.jar ... site plugins/org.jboss.tools.forge.ui.test_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.ui_1.0.0.v20120327-0403-Beta3.jar
Source Features common plugins .core artifacts.jar content.jar .ui features/org.jboss.tools.forge.feature.source_1.0.0.v20120327-0403-Beta3.jar features/org.jboss.tools.forge.feature_1.0.0.v20120327-0403-Beta3.jar ... features/org.jboss.tools.forge.test.feature.source_1.0.0.v20120327-0403-Beta3. features/org.jboss.tools.forge.test.feature_1.0.0.v20120327-0403-Beta3.jar features .feature plugins/org.jboss.tools.forge.core.source_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.core.test.source_1.0.0.v20120327-0403-Beta3.jar .source.fe plugins/org.jboss.tools.forge.core.test_1.0.0.v20120327-0403-Beta3.jar ature plugins/org.jboss.tools.forge.core_1.0.0.v20120327-0403-Beta3.jar ... plugins/org.jboss.tools.forge.runtime.ext.source_1.0.0.v20120327-0403-Beta3.ja plugins/org.jboss.tools.forge.runtime.ext_1.0.0.v20120327-0403-Beta3.jar tests .tests plugins/org.jboss.tools.forge.runtime.source_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.runtime_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.ui.source_1.0.0.v20120327-0403-Beta3.jar ... plugins/org.jboss.tools.forge.ui.test.source_1.0.0.v20120327-0403-Beta3.jar site plugins/org.jboss.tools.forge.ui.test_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.ui_1.0.0.v20120327-0403-Beta3.jar
Concise, Large Ecosystem, improving, growing, versatile, responsive community, Just Works Has had some nasty bugs - but they are fixed (0.13/0.14+) Need to understand Maven + OSGi + p2 (Speed?)
Tycho:
Tycho: just damn’good
Tycho: Resources: http://wiki.eclipse.org/Category:Tycho http://wiki.eclipse.org/Tycho/ Reference_Card http://wiki.eclipse.org/Tycho/ http://bit.ly/maxtycho Packaging_Types “Coping with versions in large multi-module osgi projects” - http://bit.ly/rTWUsq
?? ?? ? Tycho: Resources: ? ? http://wiki.eclipse.org/Category:Tycho http://wiki.eclipse.org/Tycho/ Reference_Card http://wiki.eclipse.org/Tycho/ http://bit.ly/maxtycho Packaging_Types “Coping with versions in large multi-module osgi projects” - http://bit.ly/rTWUsq
Tycho: http://bit.ly/maxtycho
?? ?? ? Tycho: ? ? http://bit.ly/maxtycho

More Related Content

KEY
How to be effective with JBoss Developer Studio
byMax Andersen
 
PDF
Enterprise Maven Repository BOF
byMax Andersen
 
PDF
JBoss Enterprise Maven Repository
byMax Andersen
 
PDF
Note - Apache Maven Intro
byboyw165
 
PDF
Build system
byAndrey Subbota
 
PDF
Liferay maven sdk
byMika Koivisto
 
PPT
Maven in Mule
byAnand kalla
 
PPTX
Apache Maven basics
byVolodymyr Ostapiv
 
How to be effective with JBoss Developer Studio
byMax Andersen
 
Enterprise Maven Repository BOF
byMax Andersen
 
JBoss Enterprise Maven Repository
byMax Andersen
 
Note - Apache Maven Intro
byboyw165
 
Build system
byAndrey Subbota
 
Liferay maven sdk
byMika Koivisto
 
Maven in Mule
byAnand kalla
 
Apache Maven basics
byVolodymyr Ostapiv
 

What's hot

PPTX
Maven
byChris Roeder
 
PDF
Jenkinsプラグインの作り方
byKiyotaka Oku
 
PPT
Maven
byjaveed_mhd
 
PPT
Maven
byAbdulImrankhan7
 
PPTX
Apache Maven 2 Part 2
byReturn on Intelligence
 
PDF
Jsf, facelets, spring, hibernate, maven2
byRaghavan Mohan
 
PDF
Maven 3 Overview
byMike Ensor
 
PPTX
Apache Maven
byvenkatraghavang
 
PDF
Maven 3… so what?
byAbel Muíño
 
PDF
Make use of Sonar for your mobile developments - It's easy and useful!
bycyrilpicat
 
PPTX
Maven
byKhan625
 
PDF
Django in the Real World
byJacob Kaplan-Moss
 
PPT
Java build tool_comparison
byManav Prasad
 
PDF
Java, Eclipse, Maven & JSF tutorial
byRaghavan Mohan
 
PDF
Hands On with Maven
bySid Anand
 
PDF
Alpes Jug (29th March, 2010) - Apache Maven
byArnaud Héritier
 
PDF
Geneva Jug (30th March, 2010) - Maven
byArnaud Héritier
 
PPTX
Apache Maven for AT/QC
byVolodymyr Ostapiv
 
PPTX
From Ant to Maven to Gradle a tale of CI tools for JVM
byBucharest Java User Group
 
PDF
[Spring Camp 2013] Java Configuration 없인 못살아!
byArawn Park
 
Maven
byChris Roeder
 
Jenkinsプラグインの作り方
byKiyotaka Oku
 
Maven
byjaveed_mhd
 
Maven
byAbdulImrankhan7
 
Apache Maven 2 Part 2
byReturn on Intelligence
 
Jsf, facelets, spring, hibernate, maven2
byRaghavan Mohan
 
Maven 3 Overview
byMike Ensor
 
Apache Maven
byvenkatraghavang
 
Maven 3… so what?
byAbel Muíño
 
Make use of Sonar for your mobile developments - It's easy and useful!
bycyrilpicat
 
Maven
byKhan625
 
Django in the Real World
byJacob Kaplan-Moss
 
Java build tool_comparison
byManav Prasad
 
Java, Eclipse, Maven & JSF tutorial
byRaghavan Mohan
 
Hands On with Maven
bySid Anand
 
Alpes Jug (29th March, 2010) - Apache Maven
byArnaud Héritier
 
Geneva Jug (30th March, 2010) - Maven
byArnaud Héritier
 
Apache Maven for AT/QC
byVolodymyr Ostapiv
 
From Ant to Maven to Gradle a tale of CI tools for JVM
byBucharest Java User Group
 
[Spring Camp 2013] Java Configuration 없인 못살아!
byArawn Park
 

Similar to Tycho - good, bad or ugly ?

KEY
企业级软件的组件化和动态化开发实践
byJacky Chi
 
PDF
JavaOne 2010: OSGI Migrat
bySAP HANA Cloud Platform
 
PPTX
Workshop OSGI PPT
bySummer Lu
 
KEY
L0016 - The Structure of an Eclipse Plug-in
byTonny Madsen
 
PDF
GlassFish v3 Lite Admin Console
byanissalam
 
PDF
Gradle talk, Javarsovia 2010
byTomek Kaczanowski
 
PDF
Of Bugs and Men (and Plugins too)
byMichel Wermelinger
 
PDF
Of Bugs and Men
byMichel Wermelinger
 
PDF
A journey with Target Platforms
byMickael Istria
 
KEY
How To Make A Framework Plugin That Does Not Suck
byMax Andersen
 
PDF
Develop Enterprise Java Applications | JBuilder
byMichael Findling
 
PPT
Java Build Tools
by­Avishek A
 
PDF
Eclipse vs Netbean vs Railo
byMohd Safian
 
PDF
How to create a skeleton of a Java console application
byDmitri Pisarenko
 
PDF
OSGi Service Platform 4.2
byIlya Katsov
 
PDF
Make Your Builds More Groovy
byPaul King
 
PDF
make builds groovy
byguest88884d
 
KEY
Jopr Plugin Development
bySEA Tecnologia
 
PDF
State of the art: Server-Side JavaScript - dejeuner fulljs
byAlexandre Morgaut
 
PDF
Crx 2.2 Deep-Dive
byGabriel Walt
 
企业级软件的组件化和动态化开发实践
byJacky Chi
 
JavaOne 2010: OSGI Migrat
bySAP HANA Cloud Platform
 
Workshop OSGI PPT
bySummer Lu
 
L0016 - The Structure of an Eclipse Plug-in
byTonny Madsen
 
GlassFish v3 Lite Admin Console
byanissalam
 
Gradle talk, Javarsovia 2010
byTomek Kaczanowski
 
Of Bugs and Men (and Plugins too)
byMichel Wermelinger
 
Of Bugs and Men
byMichel Wermelinger
 
A journey with Target Platforms
byMickael Istria
 
How To Make A Framework Plugin That Does Not Suck
byMax Andersen
 
Develop Enterprise Java Applications | JBuilder
byMichael Findling
 
Java Build Tools
by­Avishek A
 
Eclipse vs Netbean vs Railo
byMohd Safian
 
How to create a skeleton of a Java console application
byDmitri Pisarenko
 
OSGi Service Platform 4.2
byIlya Katsov
 
Make Your Builds More Groovy
byPaul King
 
make builds groovy
byguest88884d
 
Jopr Plugin Development
bySEA Tecnologia
 
State of the art: Server-Side JavaScript - dejeuner fulljs
byAlexandre Morgaut
 
Crx 2.2 Deep-Dive
byGabriel Walt
 

More from Max Andersen

PPTX
Quarkus Hidden and Forbidden Extensions
byMax Andersen
 
PDF
Quarkus Denmark 2019
byMax Andersen
 
PDF
Docker Tooling for Eclipse
byMax Andersen
 
PDF
OpenShift: Java EE in the clouds
byMax Andersen
 
PDF
Case study: JBoss Developer Studio, an IDE for Web, Mobile and Cloud applicat...
byMax Andersen
 
PDF
Red Hat and Oracle: Delivering on the Promise of Interoperability in Java EE 7
byMax Andersen
 
PDF
Google analytics for Eclipse Plugins
byMax Andersen
 
KEY
Ceylon - the language and its tools
byMax Andersen
 
KEY
Making Examples Accessible
byMax Andersen
 
PDF
OpenShift Express Intro
byMax Andersen
 
PDF
JBoss AS 7 from a user perspective
byMax Andersen
 
KEY
JBoss Asylum Podcast Live from JUDCon 2010
byMax Andersen
 
ODP
Kickstart Jpa
byMax Andersen
 
Quarkus Hidden and Forbidden Extensions
byMax Andersen
 
Quarkus Denmark 2019
byMax Andersen
 
Docker Tooling for Eclipse
byMax Andersen
 
OpenShift: Java EE in the clouds
byMax Andersen
 
Case study: JBoss Developer Studio, an IDE for Web, Mobile and Cloud applicat...
byMax Andersen
 
Red Hat and Oracle: Delivering on the Promise of Interoperability in Java EE 7
byMax Andersen
 
Google analytics for Eclipse Plugins
byMax Andersen
 
Ceylon - the language and its tools
byMax Andersen
 
Making Examples Accessible
byMax Andersen
 
OpenShift Express Intro
byMax Andersen
 
JBoss AS 7 from a user perspective
byMax Andersen
 
JBoss Asylum Podcast Live from JUDCon 2010
byMax Andersen
 
Kickstart Jpa
byMax Andersen
 

Recently uploaded

PPTX
MGw_MRS Benfits seu beficios de redes 4g
byJoaquimBarros18
 
PDF
Cross-Cultural Agile Development -Challenges and Strategies for Overcoming Them-
byTakashi Makino
 
PPTX
How to make Ai agents using Google Gemini AI.pptx
bypkluffy111
 
DOCX
iRobot Post‑Mortem and Alternative Paths - Discussion Document for Boards and...
byDave Litwiller
 
PDF
Access Control 2025: From Security Silo to Software-Defined Ecosystem
byMemoori
 
PDF
The State of the Gen AI economy - 2025 - The Meliora Company
byClive Dickens
 
PDF
WHITE PAPER_ Ransomware Payment Policy and Resilience Strategy_ A Framework f...
byssuser0d171c
 
PDF
Day 4 - Access, Deployments, and Monitoring - 2nd Sight Lab Cloud Security Class
by2nd Sight Lab
 
PDF
DevFest El Jadida 2025 - Product Thinking
byElmehdi AMLOU
 
PPTX
Top _HR Technology Trends _for 2026_.pptx
byAutomationEdge Technologies
 
PDF
Security Forum Sessions from Houston 2025 Event
byMark Simos
 
PDF
TrustArc Webinar - Looking Ahead: The 2026 Privacy Landscape
byTrustArc
 
PDF
Our Digital Tribe_ Cultivating Connection and Growth in Our Slack Community 🌿...
bysanjeetmishra30
 
PDF
Internet_of_Things_IoT_for_Next_Generation_Smart_Systems_Utilizing.pdf
byRoshanSyed12
 
PDF
Unlocking the Power of Salesforce Architecture: Frameworks for Effective Solu...
byvarsha30tiwari
 
PPTX
Building Agents in Microsoft Agent Framework.pptx
byUdaiappa Ramachandran
 
PDF
Real-Time Data Insight Using Microsoft Forms for Business
byElevate
 
PPTX
Why Most GenAI Projects Fail to Scale and How to Become One of the Success St...
byEarley Information Science
 
PDF
Fundamentals and Frontiers of Post Quantum Cryptography
byGokul Alex
 
PDF
Day 3 - Data and Application Security - 2nd Sight Lab Cloud Security Class
by2nd Sight Lab
 
MGw_MRS Benfits seu beficios de redes 4g
byJoaquimBarros18
 
Cross-Cultural Agile Development -Challenges and Strategies for Overcoming Them-
byTakashi Makino
 
How to make Ai agents using Google Gemini AI.pptx
bypkluffy111
 
iRobot Post‑Mortem and Alternative Paths - Discussion Document for Boards and...
byDave Litwiller
 
Access Control 2025: From Security Silo to Software-Defined Ecosystem
byMemoori
 
The State of the Gen AI economy - 2025 - The Meliora Company
byClive Dickens
 
WHITE PAPER_ Ransomware Payment Policy and Resilience Strategy_ A Framework f...
byssuser0d171c
 
Day 4 - Access, Deployments, and Monitoring - 2nd Sight Lab Cloud Security Class
by2nd Sight Lab
 
DevFest El Jadida 2025 - Product Thinking
byElmehdi AMLOU
 
Top _HR Technology Trends _for 2026_.pptx
byAutomationEdge Technologies
 
Security Forum Sessions from Houston 2025 Event
byMark Simos
 
TrustArc Webinar - Looking Ahead: The 2026 Privacy Landscape
byTrustArc
 
Our Digital Tribe_ Cultivating Connection and Growth in Our Slack Community 🌿...
bysanjeetmishra30
 
Internet_of_Things_IoT_for_Next_Generation_Smart_Systems_Utilizing.pdf
byRoshanSyed12
 
Unlocking the Power of Salesforce Architecture: Frameworks for Effective Solu...
byvarsha30tiwari
 
Building Agents in Microsoft Agent Framework.pptx
byUdaiappa Ramachandran
 
Real-Time Data Insight Using Microsoft Forms for Business
byElevate
 
Why Most GenAI Projects Fail to Scale and How to Become One of the Success St...
byEarley Information Science
 
Fundamentals and Frontiers of Post Quantum Cryptography
byGokul Alex
 
Day 3 - Data and Application Security - 2nd Sight Lab Cloud Security Class
by2nd Sight Lab
 

Tycho - good, bad or ugly ?

  • 1.
    Tycho: Max RydahlAndersen Red Hat at EclipseCon 2012
  • 2.
    Tycho: Max RydahlAndersen Red Hat at EclipseCon 2012
  • 3.
    •Plugins for JBossand related technology •AS, JSF, CDI, Seam, Portal, Birt, Maven, … •Top ~5 plugin on Eclipse Market Place
  • 4.
    1.200.000 starts ofJBoss Tools January-March 2012
  • 6.
    •45 modules •~8 yearold •222 plugins •PDE Ant Build •76 features •36 test features •154 test plugins
  • 7.
    •45 modules •~8 year old •222 plugins •PDE Ant Build •76 features •36 test features •154 test plugins a.k.a. The “Big Ass” Project that moved to Tycho
  • 8.
    PDE/Ant Build common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
  • 9.
    PDE/Tycho common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
  • 10.
    PDE/Tycho common plugins .core <?xml version="1.0" encoding="UTF-8"?> <project> <modelVersion>4.0.0</modelVersion> .ui <parent> <groupId>org.jboss.tools.common</groupId> ... <artifactId>plugins</artifactId> <version>3.3.0-SNAPSHOT</version> </parent> features .feature <groupId>org.jboss.tools.common.plugins</groupId> .source.fe <artifactId>org.jboss.tools.common</artifactId> ature <packaging>eclipse-plugin</packaging> </project> ... tests .tests ... site
  • 11.
    PDE/Tycho common plugins .core <?xml version="1.0" encoding="UTF-8"?> <project> <modelVersion>4.0.0</modelVersion> .ui <parent> <groupId>org.jboss.tools.common</groupId> ... <artifactId>plugins</artifactId> <version>3.3.0-SNAPSHOT</version> </parent> features .feature <groupId>org.jboss.tools.common.plugins</groupId> .source.fe <artifactId>org.jboss.tools.common</artifactId> ature <packaging>eclipse-plugin</packaging> </project> ... <packaging>eclipse-test-plugin</packaging> <packaging>eclipse-feature</packaging> tests .tests <packaging>eclipse-repository</packaging> <packaging>eclipse-application</packaging> ... site
  • 12.
    common plugins .core ”Big Ass” .ui ... features .feature .source.fe ature ... tests .tests ... site
  • 13.
    common plugins .core hibernate CDI ”Big Ass” plugins .core JSF plugins .core ... plugins .core ... plugins .core plugins .core seam plugins .core .ui .ui .ui .ui .ui .ui .ui ... ... ... ... ... features .feature ... ... .source.fe features .feature features .feature ature features .feature features .feature features .feature features .feature ... .source.fe ature .source.fe ature .source.fe .source.fe .source.fe tests .tests .source.fe ature ature ature ... ature ... ... ... ... ... tests .tests site ... tests .tests ... tests .tests tests .tests tests .tests tests .tests ... site ... site ... ... ... site site site site ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui ... ... ... ... ... ... ... ... ... ... ... ... features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe ature ature ature ature ature ature ature ature ature ature ature ature ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... ... ... ... ... ... ... ... ... ... ... ... .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature site site site site site site site site site site site site .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe ature ature ature ature ature ature ature ature ature ature ature ature ... ... ... ... ... ... ... ... ... ... ... ... tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... plugins .core ... ... ... ... ... ... ... ... ... ... ... ... .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui .ui site site site site site site site site site site site site ... ... ... ... ... ... ... ... ... ... ... ... features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature features .feature .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe .source.fe ature ature ature ature ature ature ature ature ature ature ature ature ... ... ... ... ... ... ... ... ... ... ... ... tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests tests .tests ... ... ... ... ... ... ... ... ... ... ... ... site site site site site site site site site site site site
  • 14.
    General Layout common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
  • 15.
    General Layout common plugins .core •module is a “releasable unit” .ui ... features .feature .source.fe ature ... tests .tests ... site
  • 16.
    General Layout common plugins .core •module is a “releasable unit” .ui •pom.xml at each level ... features .feature .source.fe ature ... tests .tests ... site
  • 17.
    General Layout common plugins .core •module is a “releasable unit” .ui •pom.xml at each level ... •allows to build subparts very features .feature easily .source.fe ature ... tests .tests ... site
  • 18.
    General Layout common plugins .core •module is a “releasable unit” .ui •pom.xml at each level ... •allows to build subparts very features .feature easily .source.fe •separate customization for ature modules ... tests .tests ... site
  • 19.
    General Layout common plugins .core •module is a “releasable unit” .ui •pom.xml at each level ... •allows to build subparts very features .feature easily .source.fe •separate customization for ature modules •Can use mvn version per module ... tests .tests ... site
  • 20.
    tycho-versions-plugin common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
  • 21.
    tycho-versions-plugin common plugins .core 1.0.2 2.0.1 2.0.1 .ui 1.0.3 ... 1.1.2 features .feature 2.0.1 2.0.1 .source.fe ature 2.0.1 ... 1.1.2 tests .tests 1.1.2 2.0.1 ... 1.1.2 site 1.1.3
  • 22.
    tycho-versions-plugin common plugins .core 1.0.2 2.0.1 2.0.1 .ui 1.0.3 ... 1.1.2 mvn org.eclipse.tycho:tycho-versions- features .feature 2.0.1 plugin:set-version -DnewVersion=2.0.2 2.0.1 .source.fe ature 2.0.1 ... 1.1.2 tests .tests 1.1.2 2.0.1 ... 1.1.2 site 1.1.3
  • 23.
    tycho-versions-plugin common plugins .core 1.0.2 2.0.2 2.0.2 .ui 1.0.3 ... 1.1.2 features .feature 2.0.2 2.0.2 .source.fe ature 2.0.2 ... 1.1.2 tests .tests 1.1.2 2.0.2 ... 1.1.2 site 1.1.3
  • 24.
    tycho-versions-plugin common plugins .core 2.0.2 2.0.2 2.0.2 .ui 2.0.2 ... 2.0.2 features .feature 2.0.2 2.0.2 .source.fe ature 2.0.2 ... 2.0.2 tests .tests 2.0.2 2.0.2 ... 2.0.2 site 2.0.2
  • 25.
    tycho-versions-plugin common plugins .core 2.0.2 2.0.2 2.0.2 .ui 2.0.2 ... 2.0.2 mvn org.eclipse.tycho:tycho-versions- features .feature 2.0.2 plugin:set-version -DnewVersion=2.1.0 2.0.2 .source.fe ature 2.0.2 ... 2.0.2 tests .tests 2.0.2 2.0.2 ... 2.0.2 site 2.0.2
  • 26.
    tycho-versions-plugin common plugins .core 2.1.0 2.1.0 2.1.0 .ui 2.1.0 ... 2.1.0 features .feature 2.1.0 2.1.0 .source.fe ature 2.1.0 ... 2.1.0 tests .tests 2.1.0 2.1.0 ... 2.1.0 site 2.1.0
  • 27.
    tycho-versions-plugin common plugins .core 1.7.3 2.1.0 2.1.0 .ui 2.1.0 ... 2.1.0 features .feature 2.1.0 2.1.0 .source.fe ature 2.1.0 ... 2.1.0 tests .tests 2.1.0 2.1.0 ... 2.1.0 site 2.1.0
  • 28.
    tycho-versions-plugin common plugins .core 1.7.3 2.1.0 2.1.0 .ui 2.1.0 ... 2.1.0 mvn org.eclipse.tycho:tycho-versions- features .feature 2.1.0 plugin:set-version -DnewVersion=2.1.1 2.1.0 .source.fe ature 2.1.0 ... 2.1.0 tests .tests 2.1.0 2.1.0 ... 2.1.0 site 2.1.0
  • 29.
    tycho-versions-plugin common plugins .core 1.7.3 2.1.1 2.1.1 .ui 2.1.1 ... 2.1.1 features .feature 2.1.1 2.1.1 .source.fe ature 2.1.1 ... 2.1.1 tests .tests 2.1.1 2.1.1 ... 2.1.1 site 2.1.1
  • 30.
    tycho-versions-plugin common plugins .core 1.7.3 2.1.1 2.1.1 .ui 2.1.1 •Easy update of versions in ... 2.1.1 •pom.xml •manifest.mf features .feature 2.1.1 •feature.xml 2.1.1 .source.fe ature 2.1.1 •site.xml ... 2.1.1 •.product tests .tests 2.1.1 •…. 2.1.1 ... 2.1.1 •Don’t Repeat Yourself site 2.1.1
  • 31.
    Plugin A Require-Bundle: Z [1.2;2.0] Plugin B Plugin C Require-Bundle: Z [1.7;2.0] Source
  • 32.
    Plugin A Require-Bundle: Z [1.2;2.0] Plugin B Plugin C Require-Bundle: Z [1.7;2.0] Source ~/.m2/repository
  • 33.
    Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Q 1.2.1 Plugin B Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source ~/.m2/repository
  • 34.
    Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Q 1.2.1 Plugin B Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin Z 1.8 ~/.m2/repository
  • 35.
    Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Q 1.2.1 Plugin B Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin B 1.2.3 Plugin C Plugin Z 1.8 1.2.3 Plugin A 1.2.3 ~/.m2/repository
  • 36.
    Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source ~/.m2/repository
  • 37.
    Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin Z 1.7 Plugin Q 1.2.1 ~/.m2/repository
  • 38.
    Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin C 1.2.3 Plugin A Plugin Q 1.2.1 1.2.3 ~/.m2/repository
  • 39.
    Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin C 1.2.3 Plugin A Plugin Q 1.2.1 1.2.3 ~/.m2/repository
  • 40.
    Plugin A p2 repositories Require-Bundle: Z [1.2;2.0] Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin B Target Definition Plugin Z 1.7 Plugin Z 1.8 Plugin C Require-Bundle: Z [1.7;2.0] Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin C Plugin B 1.2.3 1.2.3 Plugin A Plugin Q 1.2.1 1.2.3 Plugin A 1.2.3 ~/.m2/repository
  • 41.
    p2 repositories Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin C Target Definition Plugin Z 1.7 Require-Bundle: Z Plugin Z 1.8 [1.7;2.0] B Plugin Z 2.0 Source Plugin B 1.2.3 Plugin A 1.2.3 ~/.m2/repository
  • 42.
    p2 repositories Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin C Target Definition Plugin Z 1.7 Require-Bundle: Z Plugin Z 1.8 [1.7;2.0] B Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin B 1.2.3 Plugin Q 1.2.1 Plugin A 1.2.3 ~/.m2/repository
  • 43.
    p2 repositories Plugin Z 1.7 Plugin Q Plugin Q 1.2.1 Plugin C Target Definition Plugin Z 1.7 Require-Bundle: Z Plugin Z 1.8 [1.7;2.0] B Plugin Z 2.0 Source Plugin B Plugin Z 1.7 1.2.3 Plugin B 1.2.3 Plugin C Plugin Q 1.2.1 1.2.3 Plugin A 1.2.3 ~/.m2/repository
  • 44.
  • 45.
  • 46.
  • 47.
  • 48.
  • 49.
  • 50.
    0.13+ ! ! <format>'v'yyyyMMdd-HHmm'-${BID}'</format>
  • 51.
    Update Sites common plugins .core artifacts.jar content.jar .ui features/org.jboss.tools.forge.feature_1.0.0.v20120327-0403-Beta3.jar ... features/org.jboss.tools.forge.test.feature_1.0.0.v20120327-0403-Beta3.jar features .feature .source.fe plugins/org.jboss.tools.forge.core.test_1.0.0.v20120327-0403-Beta3.jar ature plugins/org.jboss.tools.forge.core_1.0.0.v20120327-0403-Beta3.jar ... plugins/org.jboss.tools.forge.runtime.ext_1.0.0.v20120327-0403-Beta3.jar tests .tests plugins/org.jboss.tools.forge.runtime_1.0.0.v20120327-0403-Beta3.jar ... site plugins/org.jboss.tools.forge.ui.test_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.ui_1.0.0.v20120327-0403-Beta3.jar
  • 52.
    Source Features common plugins .core .ui ... features .feature .source.fe ature ... tests .tests ... site
  • 53.
    Source Features <plugins> common plugins .core <plugin> <groupId>org.eclipse.tycho.extras</groupId> <artifactId>tycho-source-feature-plugin</artifactId> .ui <version>${tychoVersion}</version> <executions> <execution> ... <id>source-feature</id> <phase>package</phase> <goals> features .feature <goal>source-feature</goal> </goals> </execution> .source.fe </executions> ature </plugin> <plugin> ... <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-p2-plugin</artifactId> <version>${tychoVersion}</version> tests .tests <executions> <execution> <id>attached-p2-metadata</id> <phase>package</phase> ... <goals> <goal>p2-metadata</goal> site </goals> </execution> </executions> </plugin> </plugins>
  • 54.
    Source Features <plugins> common plugins .core <plugin> <groupId>org.eclipse.tycho.extras</groupId> <artifactId>tycho-source-feature-plugin</artifactId> .ui <version>${tychoVersion}</version> <executions> <execution> ... <id>source-feature</id> <phase>package</phase> <goals> features .feature <goal>source-feature</goal> </goals> </execution> .source.fe </executions> ature </plugin> <plugin> ... <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-p2-plugin</artifactId> <version>${tychoVersion}</version> tests .tests <executions> <execution> <id>attached-p2-metadata</id> <phase>package</phase> ... <goals> <goal>p2-metadata</goal> site </goals> </execution> 0.14+ </executions> </plugin> </plugins>
  • 55.
    Source Features <plugins> common plugins .core <plugin> <groupId>org.eclipse.tycho.extras</groupId> <artifactId>tycho-source-feature-plugin</artifactId> .ui <version>${tychoVersion}</version> <executions> <execution> ... <id>source-feature</id> <phase>package</phase> <goals> features .feature <goal>source-feature</goal> </goals> </execution> .source.fe </executions> ature </plugin> <plugin> ... <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-p2-plugin</artifactId> <version>${tychoVersion}</version> tests .tests <executions> <execution> <id>attached-p2-metadata</id> <phase>package</phase> ... <goals> <goal>p2-metadata</goal> site </goals> </execution> </executions> </plugin> </plugins>
  • 56.
    Source Features common plugins .core artifacts.jar content.jar .ui features/org.jboss.tools.forge.feature_1.0.0.v20120327-0403-Beta3.jar ... features/org.jboss.tools.forge.test.feature_1.0.0.v20120327-0403-Beta3.jar features .feature .source.fe plugins/org.jboss.tools.forge.core.test_1.0.0.v20120327-0403-Beta3.jar ature plugins/org.jboss.tools.forge.core_1.0.0.v20120327-0403-Beta3.jar ... plugins/org.jboss.tools.forge.runtime.ext_1.0.0.v20120327-0403-Beta3.jar tests .tests plugins/org.jboss.tools.forge.runtime_1.0.0.v20120327-0403-Beta3.jar ... site plugins/org.jboss.tools.forge.ui.test_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.ui_1.0.0.v20120327-0403-Beta3.jar
  • 57.
    Source Features common plugins .core artifacts.jar content.jar .ui features/org.jboss.tools.forge.feature.source_1.0.0.v20120327-0403-Beta3.jar features/org.jboss.tools.forge.feature_1.0.0.v20120327-0403-Beta3.jar ... features/org.jboss.tools.forge.test.feature.source_1.0.0.v20120327-0403-Beta3. features/org.jboss.tools.forge.test.feature_1.0.0.v20120327-0403-Beta3.jar features .feature plugins/org.jboss.tools.forge.core.source_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.core.test.source_1.0.0.v20120327-0403-Beta3.jar .source.fe plugins/org.jboss.tools.forge.core.test_1.0.0.v20120327-0403-Beta3.jar ature plugins/org.jboss.tools.forge.core_1.0.0.v20120327-0403-Beta3.jar ... plugins/org.jboss.tools.forge.runtime.ext.source_1.0.0.v20120327-0403-Beta3.ja plugins/org.jboss.tools.forge.runtime.ext_1.0.0.v20120327-0403-Beta3.jar tests .tests plugins/org.jboss.tools.forge.runtime.source_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.runtime_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.ui.source_1.0.0.v20120327-0403-Beta3.jar ... plugins/org.jboss.tools.forge.ui.test.source_1.0.0.v20120327-0403-Beta3.jar site plugins/org.jboss.tools.forge.ui.test_1.0.0.v20120327-0403-Beta3.jar plugins/org.jboss.tools.forge.ui_1.0.0.v20120327-0403-Beta3.jar
  • 59.
    Concise, Large Ecosystem,improving, growing, versatile, responsive community, Just Works Has had some nasty bugs - but they are fixed (0.13/0.14+) Need to understand Maven + OSGi + p2 (Speed?)
  • 60.
  • 61.
  • 62.
    Tycho: Resources: http://wiki.eclipse.org/Category:Tycho http://wiki.eclipse.org/Tycho/ Reference_Card http://wiki.eclipse.org/Tycho/ http://bit.ly/maxtycho Packaging_Types “Coping with versions in large multi-module osgi projects” - http://bit.ly/rTWUsq
  • 63.
    ?? ?? ? Tycho: Resources: ? ? http://wiki.eclipse.org/Category:Tycho http://wiki.eclipse.org/Tycho/ Reference_Card http://wiki.eclipse.org/Tycho/ http://bit.ly/maxtycho Packaging_Types “Coping with versions in large multi-module osgi projects” - http://bit.ly/rTWUsq
  • 64.
  • 65.
    ?? ?? ? Tycho: ? ? http://bit.ly/maxtycho

Editor's Notes

  • #2 I&amp;#x2019;m here to talk about the good, bad and ugly sides of Tycho.\nMy name is Max Andersen I work for Red Hat and I work on the project named...\n
  • #3 I&amp;#x2019;m here to talk about the good, bad and ugly sides of Tycho.\nMy name is Max Andersen I work for Red Hat and I work on the project named...\n
  • #4 ...JBoss Tools. JBoss Tools is a set of plugins which focus on JBoss and related technology to make development experience around JBoss better. Tech such as AS it self, JSF, CDI, Seam, Birt, Maven etc. and we are in the top on eclipse market place for usage.\n
  • #5 Which means we are used all around the world - these are showing the last 3 months &amp;#x201C;pings&amp;#x201D; to our usage plugin showing the distribution of a million startups. One of my favorite slides :)\n
  • #6 But i&amp;#x2019;m here to talk about jboss tools in context of builds - and we are an old project, almost as old as eclipse it self and we&amp;#x2019;ve seen all the various build techs come and go but until Tycho came around we stayed with PDE ant build. Our project is rather big - a lot of modules, plugins and features whick makes us a.ka. the Big Ass project that moved to Tycho\n
  • #7 But i&amp;#x2019;m here to talk about jboss tools in context of builds - and we are an old project, almost as old as eclipse it self and we&amp;#x2019;ve seen all the various build techs come and go but until Tycho came around we stayed with PDE ant build. Our project is rather big - a lot of modules, plugins and features whick makes us a.ka. the Big Ass project that moved to Tycho\n
  • #8 But i&amp;#x2019;m here to talk about jboss tools in context of builds - and we are an old project, almost as old as eclipse it self and we&amp;#x2019;ve seen all the various build techs come and go but until Tycho came around we stayed with PDE ant build. Our project is rather big - a lot of modules, plugins and features whick makes us a.ka. the Big Ass project that moved to Tycho\n
  • #9 So lets take a look at how our module(s) looked like when we used PDE/Ant Build. We had a root for each module, under here plugins/features/tests and site with their respective bundles/plugins/content. So what happens with this when moving to Tycho...?\n
  • #10 ..absolutely nothing. And this is the reason why Tycho was able to get us off PDE ant build! Thank you! Of course we did have to add a pom.xml here and there...\n
  • #11 ..actually everywhere ;) each level in that structure has a pom.xml but thankfully they are for most very concise. You simply just state the GAV (group,artifact,version) for you artifact and then the packaging. in this case it is eclipse-plugin but &lt;click&gt; there is also a packaging for every other important eclipse packaging. Great stuff! This structure is our general layout..\n
  • #12 ..actually everywhere ;) each level in that structure has a pom.xml but thankfully they are for most very concise. You simply just state the GAV (group,artifact,version) for you artifact and then the packaging. in this case it is eclipse-plugin but &lt;click&gt; there is also a packaging for every other important eclipse packaging. Great stuff! This structure is our general layout..\n
  • #13 ..actually everywhere ;) each level in that structure has a pom.xml but thankfully they are for most very concise. You simply just state the GAV (group,artifact,version) for you artifact and then the packaging. in this case it is eclipse-plugin but &lt;click&gt; there is also a packaging for every other important eclipse packaging. Great stuff! This structure is our general layout..\n
  • #14 ..actually everywhere ;) each level in that structure has a pom.xml but thankfully they are for most very concise. You simply just state the GAV (group,artifact,version) for you artifact and then the packaging. in this case it is eclipse-plugin but &lt;click&gt; there is also a packaging for every other important eclipse packaging. Great stuff! This structure is our general layout..\n
  • #15 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #16 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #17 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #18 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #19 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #20 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #21 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #22 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #23 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #24 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #25 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #26 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #27 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #28 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #29 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #30 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #31 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #32 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #33 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #34 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #35 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #36 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #37 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #38 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #39 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #40 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #41 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #42 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #43 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #44 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #45 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #46 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #47 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #48 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #49 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #50 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #51 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #52 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #53 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #54 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #55 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #56 ..and is used with everyone of our modules ...and &lt;click&gt; ...there is alot of them. and when I say Alot I mean alot. I didn&amp;#x2019;t call it Big Ass for nothing.\n
  • #57 ...this general layout which I actually don&amp;#x2019;t know from where we got it actually turned out to be pretty good for us. It allows us to &lt;click&gt; think about each module as a releasable unit (we don&amp;#x2019;t use that alot yet, but for build setup its very nice). A downside is the extra pom&amp;#x2019;s at each level but the great thing is that it allow us to &lt;click&gt; build subparts very easily and something we hadn&amp;#x2019;t thought about upfront was that it actually gave a nice natural place for modules to &lt;click&gt; customize their testing setup if need be or if a module had special needs compared to what is defined in the maven parent. And something that I&amp;#x2019;ve learned to love &lt;click&gt; is that because there now is a structure defined across the whole module we can use mvn tools such as mvn version plugins to manage all this stuff. Something that pde ant never did.\n
  • #58 ...this general layout which I actually don&amp;#x2019;t know from where we got it actually turned out to be pretty good for us. It allows us to &lt;click&gt; think about each module as a releasable unit (we don&amp;#x2019;t use that alot yet, but for build setup its very nice). A downside is the extra pom&amp;#x2019;s at each level but the great thing is that it allow us to &lt;click&gt; build subparts very easily and something we hadn&amp;#x2019;t thought about upfront was that it actually gave a nice natural place for modules to &lt;click&gt; customize their testing setup if need be or if a module had special needs compared to what is defined in the maven parent. And something that I&amp;#x2019;ve learned to love &lt;click&gt; is that because there now is a structure defined across the whole module we can use mvn tools such as mvn version plugins to manage all this stuff. Something that pde ant never did.\n
  • #59 ...this general layout which I actually don&amp;#x2019;t know from where we got it actually turned out to be pretty good for us. It allows us to &lt;click&gt; think about each module as a releasable unit (we don&amp;#x2019;t use that alot yet, but for build setup its very nice). A downside is the extra pom&amp;#x2019;s at each level but the great thing is that it allow us to &lt;click&gt; build subparts very easily and something we hadn&amp;#x2019;t thought about upfront was that it actually gave a nice natural place for modules to &lt;click&gt; customize their testing setup if need be or if a module had special needs compared to what is defined in the maven parent. And something that I&amp;#x2019;ve learned to love &lt;click&gt; is that because there now is a structure defined across the whole module we can use mvn tools such as mvn version plugins to manage all this stuff. Something that pde ant never did.\n
  • #60 ...this general layout which I actually don&amp;#x2019;t know from where we got it actually turned out to be pretty good for us. It allows us to &lt;click&gt; think about each module as a releasable unit (we don&amp;#x2019;t use that alot yet, but for build setup its very nice). A downside is the extra pom&amp;#x2019;s at each level but the great thing is that it allow us to &lt;click&gt; build subparts very easily and something we hadn&amp;#x2019;t thought about upfront was that it actually gave a nice natural place for modules to &lt;click&gt; customize their testing setup if need be or if a module had special needs compared to what is defined in the maven parent. And something that I&amp;#x2019;ve learned to love &lt;click&gt; is that because there now is a structure defined across the whole module we can use mvn tools such as mvn version plugins to manage all this stuff. Something that pde ant never did.\n
  • #61 ...this general layout which I actually don&amp;#x2019;t know from where we got it actually turned out to be pretty good for us. It allows us to &lt;click&gt; think about each module as a releasable unit (we don&amp;#x2019;t use that alot yet, but for build setup its very nice). A downside is the extra pom&amp;#x2019;s at each level but the great thing is that it allow us to &lt;click&gt; build subparts very easily and something we hadn&amp;#x2019;t thought about upfront was that it actually gave a nice natural place for modules to &lt;click&gt; customize their testing setup if need be or if a module had special needs compared to what is defined in the maven parent. And something that I&amp;#x2019;ve learned to love &lt;click&gt; is that because there now is a structure defined across the whole module we can use mvn tools such as mvn version plugins to manage all this stuff. Something that pde ant never did.\n
  • #62 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #63 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #64 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #65 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #66 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #67 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #68 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #69 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #70 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #71 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #72 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #73 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #74 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #75 ...so to explain this here you see the layout for one of our modules - this time with versions - in this setup everything is all over the map, something some project is ok with others not so much since they release the whole module not individual parts of it. So lets try use the mvn version plugin on this stuff. &lt;click&gt; We start by wanting to bump 2.0.1 to 2.0.2&amp;#x2026; \n
  • #76 ...mvn tycho will now go through all the pom&amp;#x2019;s/manifest/feature etc. where it can safely do the bump and you end up with something like this&amp;#x2026;.still alot of manual maintanence and for many of our plugins alot of manual tweaking.\n
  • #77 ..thus we&amp;#x2019;ve made it so we just have the version listed in the top module root and now &lt;click&gt; when we bump versions with tycho it actually bumps them all.\n
  • #78 ...it might be hard for you guys to appreciate the impact of this but we have over 645 versionable artifact (for good and some bad reasons) and having this kind of automation is awesome.\n
  • #79 ...some don&amp;#x2019;t like this approach and here I just have to point out that you can of course if you project needs it have parts of your module that is versioned very strictly and still benefit from this on the artifacts where the version is more tied to the overall release.&lt;click&gt;\n
  • #80 to sum up - the fact we moved to tycho gave us maven, which despite its reputation actually does provide great value to us because its possible to have tools work on the more powerful project model it provides over plain PDE build setups. Beyond the easy update of versions in all these artifacts - the fact I don&amp;#x2019;t have to see us repeat our self with respect to versions makes me happy...and remember version plugin is just one of them. code coverage, sonar, build setup etc. is others - I just took this one since its a not well knwon feature of tycho.\n
  • #81 to sum up - the fact we moved to tycho gave us maven, which despite its reputation actually does provide great value to us because its possible to have tools work on the more powerful project model it provides over plain PDE build setups. Beyond the easy update of versions in all these artifacts - the fact I don&amp;#x2019;t have to see us repeat our self with respect to versions makes me happy...and remember version plugin is just one of them. code coverage, sonar, build setup etc. is others - I just took this one since its a not well knwon feature of tycho.\n
  • #82 to sum up - the fact we moved to tycho gave us maven, which despite its reputation actually does provide great value to us because its possible to have tools work on the more powerful project model it provides over plain PDE build setups. Beyond the easy update of versions in all these artifacts - the fact I don&amp;#x2019;t have to see us repeat our self with respect to versions makes me happy...and remember version plugin is just one of them. code coverage, sonar, build setup etc. is others - I just took this one since its a not well knwon feature of tycho.\n
  • #83 to sum up - the fact we moved to tycho gave us maven, which despite its reputation actually does provide great value to us because its possible to have tools work on the more powerful project model it provides over plain PDE build setups. Beyond the easy update of versions in all these artifacts - the fact I don&amp;#x2019;t have to see us repeat our self with respect to versions makes me happy...and remember version plugin is just one of them. code coverage, sonar, build setup etc. is others - I just took this one since its a not well knwon feature of tycho.\n
  • #84 to sum up - the fact we moved to tycho gave us maven, which despite its reputation actually does provide great value to us because its possible to have tools work on the more powerful project model it provides over plain PDE build setups. Beyond the easy update of versions in all these artifacts - the fact I don&amp;#x2019;t have to see us repeat our self with respect to versions makes me happy...and remember version plugin is just one of them. code coverage, sonar, build setup etc. is others - I just took this one since its a not well knwon feature of tycho.\n
  • #85 to sum up - the fact we moved to tycho gave us maven, which despite its reputation actually does provide great value to us because its possible to have tools work on the more powerful project model it provides over plain PDE build setups. Beyond the easy update of versions in all these artifacts - the fact I don&amp;#x2019;t have to see us repeat our self with respect to versions makes me happy...and remember version plugin is just one of them. code coverage, sonar, build setup etc. is others - I just took this one since its a not well knwon feature of tycho.\n
  • #86 to sum up - the fact we moved to tycho gave us maven, which despite its reputation actually does provide great value to us because its possible to have tools work on the more powerful project model it provides over plain PDE build setups. Beyond the easy update of versions in all these artifacts - the fact I don&amp;#x2019;t have to see us repeat our self with respect to versions makes me happy...and remember version plugin is just one of them. code coverage, sonar, build setup etc. is others - I just took this one since its a not well knwon feature of tycho.\n
  • #87 to sum up - the fact we moved to tycho gave us maven, which despite its reputation actually does provide great value to us because its possible to have tools work on the more powerful project model it provides over plain PDE build setups. Beyond the easy update of versions in all these artifacts - the fact I don&amp;#x2019;t have to see us repeat our self with respect to versions makes me happy...and remember version plugin is just one of them. code coverage, sonar, build setup etc. is others - I just took this one since its a not well knwon feature of tycho.\n
  • #88 Another aspect of tycho is the whole &amp;#x201C;getting and resolving dependencies mechanism&amp;#x201D;. something that you in PDE had to do manually and in many time machine specific ways. With tycho you have your source and since it uses mvn an .m2 repository local on disk. Here the build will fail because of the missing Plugin Z - and thus you &lt;click&gt; would go and add a p2 repository (or more) to your build. Now with that repository available tycho can create an implicit target platform by getting the missing Z from the repo and then &lt;click&gt; build A,B and C. Easy stuff - but what if what you actually wanted was Plugin Z 1.7 ? what happens if you p2 repo gets a new 1.9 version ? Your build will be affected by it!\n
  • #89 Another aspect of tycho is the whole &amp;#x201C;getting and resolving dependencies mechanism&amp;#x201D;. something that you in PDE had to do manually and in many time machine specific ways. With tycho you have your source and since it uses mvn an .m2 repository local on disk. Here the build will fail because of the missing Plugin Z - and thus you &lt;click&gt; would go and add a p2 repository (or more) to your build. Now with that repository available tycho can create an implicit target platform by getting the missing Z from the repo and then &lt;click&gt; build A,B and C. Easy stuff - but what if what you actually wanted was Plugin Z 1.7 ? what happens if you p2 repo gets a new 1.9 version ? Your build will be affected by it!\n
  • #90 Another aspect of tycho is the whole &amp;#x201C;getting and resolving dependencies mechanism&amp;#x201D;. something that you in PDE had to do manually and in many time machine specific ways. With tycho you have your source and since it uses mvn an .m2 repository local on disk. Here the build will fail because of the missing Plugin Z - and thus you &lt;click&gt; would go and add a p2 repository (or more) to your build. Now with that repository available tycho can create an implicit target platform by getting the missing Z from the repo and then &lt;click&gt; build A,B and C. Easy stuff - but what if what you actually wanted was Plugin Z 1.7 ? what happens if you p2 repo gets a new 1.9 version ? Your build will be affected by it!\n
  • #91 Another aspect of tycho is the whole &amp;#x201C;getting and resolving dependencies mechanism&amp;#x201D;. something that you in PDE had to do manually and in many time machine specific ways. With tycho you have your source and since it uses mvn an .m2 repository local on disk. Here the build will fail because of the missing Plugin Z - and thus you &lt;click&gt; would go and add a p2 repository (or more) to your build. Now with that repository available tycho can create an implicit target platform by getting the missing Z from the repo and then &lt;click&gt; build A,B and C. Easy stuff - but what if what you actually wanted was Plugin Z 1.7 ? what happens if you p2 repo gets a new 1.9 version ? Your build will be affected by it!\n
  • #92 Another aspect of tycho is the whole &amp;#x201C;getting and resolving dependencies mechanism&amp;#x201D;. something that you in PDE had to do manually and in many time machine specific ways. With tycho you have your source and since it uses mvn an .m2 repository local on disk. Here the build will fail because of the missing Plugin Z - and thus you &lt;click&gt; would go and add a p2 repository (or more) to your build. Now with that repository available tycho can create an implicit target platform by getting the missing Z from the repo and then &lt;click&gt; build A,B and C. Easy stuff - but what if what you actually wanted was Plugin Z 1.7 ? what happens if you p2 repo gets a new 1.9 version ? Your build will be affected by it!\n
  • #93 Another aspect of tycho is the whole &amp;#x201C;getting and resolving dependencies mechanism&amp;#x201D;. something that you in PDE had to do manually and in many time machine specific ways. With tycho you have your source and since it uses mvn an .m2 repository local on disk. Here the build will fail because of the missing Plugin Z - and thus you &lt;click&gt; would go and add a p2 repository (or more) to your build. Now with that repository available tycho can create an implicit target platform by getting the missing Z from the repo and then &lt;click&gt; build A,B and C. Easy stuff - but what if what you actually wanted was Plugin Z 1.7 ? what happens if you p2 repo gets a new 1.9 version ? Your build will be affected by it!\n
  • #94 ...to help on that Tycho supports target definitions - here I can specify the Z plugin specific version and I can even add other plugins to the target platform which might not be explicitly needed by the plugin but might be relevant for actually running tests for this build. Same approach again &lt;click&gt; tycho gets the plugin Z but now uses 1.7 and it also grabs the Q to do the build and after that &lt;click&gt; Tycho can again build A,B and C.\n
  • #95 ...to help on that Tycho supports target definitions - here I can specify the Z plugin specific version and I can even add other plugins to the target platform which might not be explicitly needed by the plugin but might be relevant for actually running tests for this build. Same approach again &lt;click&gt; tycho gets the plugin Z but now uses 1.7 and it also grabs the Q to do the build and after that &lt;click&gt; Tycho can again build A,B and C.\n
  • #96 ...to help on that Tycho supports target definitions - here I can specify the Z plugin specific version and I can even add other plugins to the target platform which might not be explicitly needed by the plugin but might be relevant for actually running tests for this build. Same approach again &lt;click&gt; tycho gets the plugin Z but now uses 1.7 and it also grabs the Q to do the build and after that &lt;click&gt; Tycho can again build A,B and C.\n
  • #97 ...to help on that Tycho supports target definitions - here I can specify the Z plugin specific version and I can even add other plugins to the target platform which might not be explicitly needed by the plugin but might be relevant for actually running tests for this build. Same approach again &lt;click&gt; tycho gets the plugin Z but now uses 1.7 and it also grabs the Q to do the build and after that &lt;click&gt; Tycho can again build A,B and C.\n
  • #98 ...to help on that Tycho supports target definitions - here I can specify the Z plugin specific version and I can even add other plugins to the target platform which might not be explicitly needed by the plugin but might be relevant for actually running tests for this build. Same approach again &lt;click&gt; tycho gets the plugin Z but now uses 1.7 and it also grabs the Q to do the build and after that &lt;click&gt; Tycho can again build A,B and C.\n
  • #99 Now what if I wanted to build C on its own - do I still need to check out A &amp; B to build ? no, you can actually &lt;click&gt;publish your results to a p2 repository (in reality its just a directory on an http server) and you as a user can do that or your hudson build can do it and other builds can now pick it up.\n
  • #100 Now what if I wanted to build C on its own - do I still need to check out A &amp; B to build ? no, you can actually &lt;click&gt;publish your results to a p2 repository (in reality its just a directory on an http server) and you as a user can do that or your hudson build can do it and other builds can now pick it up.\n
  • #101 Now what if I wanted to build C on its own - do I still need to check out A &amp; B to build ? no, you can actually &lt;click&gt;publish your results to a p2 repository (in reality its just a directory on an http server) and you as a user can do that or your hudson build can do it and other builds can now pick it up.\n
  • #102 ...so how does that work ? well you just have your C plugin checked out and for this example i stated that C needs Z and B. Now because my latest builds are available in the p2 repositories tycho &lt;click&gt; is again able to create a target platform &lt;click&gt; that allows me to build C&amp;#x2026;.so we used this setup but it actually gave us a lesson in time.\n
  • #103 ...so how does that work ? well you just have your C plugin checked out and for this example i stated that C needs Z and B. Now because my latest builds are available in the p2 repositories tycho &lt;click&gt; is again able to create a target platform &lt;click&gt; that allows me to build C&amp;#x2026;.so we used this setup but it actually gave us a lesson in time.\n
  • #104 ...so how does that work ? well you just have your C plugin checked out and for this example i stated that C needs Z and B. Now because my latest builds are available in the p2 repositories tycho &lt;click&gt; is again able to create a target platform &lt;click&gt; that allows me to build C&amp;#x2026;.so we used this setup but it actually gave us a lesson in time.\n
  • #105 ...so how does that work ? well you just have your C plugin checked out and for this example i stated that C needs Z and B. Now because my latest builds are available in the p2 repositories tycho &lt;click&gt; is again able to create a target platform &lt;click&gt; that allows me to build C&amp;#x2026;.so we used this setup but it actually gave us a lesson in time.\n
  • #106 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #107 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #108 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #109 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #110 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #111 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #112 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #113 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #114 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #115 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #116 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #117 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #118 Tycho is very good at matching how PDE/p2 is normally used by having .qualifiers and replace it with a real qualifier. its default a timestamp but you can also override it as shown here. the timpestamp is what caught us offguard since we have &lt;click&gt; a build server in eastern us - our hudson instance lives there...and our team and community builds against it from all over the world. Now what happend is that tycho had a bug that made the build look as they were always done &amp;#x201C;back in time&amp;#x201D; and thus users local builds in Eu/Asia was hornored first, but those living behind that red line saw their builds sometime pickup old stuff because the timestamp was &amp;#x201C;ahead of time&amp;#x201D;.\n
  • #119 luckily in 0.13 they fixed this and just like traditional mvn this qualifier is now generated with an UTC timestamp and not a local one! So at least use 0.13 if you are in a world wide team.\n
  • #120 Another great thing about Tycho is that it generates updatesites just as easy as it builds plugins - since it has all the right metadata to do this based on the existing PDE build.properties and manifest.mf files it just works....but some things are missing in this picture...and that is...&lt;click&gt;\n
  • #121 Source features - I want our technical users to be able to see how we build the features they are using and let them contribute back easily. For that we need source Eclipse features. This before tycho required a lot of templating code and tedius setup and repetition.&lt;click&gt; in tycho it just requires a bunch of xml noise.&lt;click&gt;p.s. all this only work in 0.14+ &lt;click&gt;\n
  • #122 Source features - I want our technical users to be able to see how we build the features they are using and let them contribute back easily. For that we need source Eclipse features. This before tycho required a lot of templating code and tedius setup and repetition.&lt;click&gt; in tycho it just requires a bunch of xml noise.&lt;click&gt;p.s. all this only work in 0.14+ &lt;click&gt;\n
  • #123 The interesting part are that you just need to enable source-feature packaging and enable a p2-metadata generation of these during packaging.\nWhat are we getting for adding this bunch of xml ?\n
  • #124 Before we had the updatesite as we were used to it...\n
  • #125 Now we have source features in there - all nicely installable and reusable. Greatness! Just one of the many upsides of marrying maven and p2; it might not be perfect in the beginning but generally the end result is so much worth it.\n
  • #126 ...but time is short and its time to try and sum up what is good, bad and ugly about Tycho &lt;click&gt;. The good is that this stuff just works - the additional metadata is concise and opens up to use all the great stuff happening in the mvn ecosystem. And something I haven&amp;#x2019;t highlighted here is that the guys from sonatype and SAP and others are very active on the mailing list to help figure out the tricky corners and fix bugs you helped identify. The Bad side is that there are bugs and there have been some nasty ones but luckily most of these are fixed in 0.13 and onwards and I hope at tonight BOF&amp;#x2019;s we can tackle some of the left over issues&amp;#x2026; and if there is one ugly thing I should say about these is that to setup Tycho you need to understand mvn, osgi and P2 - and that is a challenge...but the same challenge also existed with PDE/Build and the power of tycho is that because it is much more strict it actually helped us to cleanup things we ignored or didnt realize was true problems for p2/osgi until Tycho told us differently.\n
  • #127 ...but time is short and its time to try and sum up what is good, bad and ugly about Tycho &lt;click&gt;. The good is that this stuff just works - the additional metadata is concise and opens up to use all the great stuff happening in the mvn ecosystem. And something I haven&amp;#x2019;t highlighted here is that the guys from sonatype and SAP and others are very active on the mailing list to help figure out the tricky corners and fix bugs you helped identify. The Bad side is that there are bugs and there have been some nasty ones but luckily most of these are fixed in 0.13 and onwards and I hope at tonight BOF&amp;#x2019;s we can tackle some of the left over issues&amp;#x2026; and if there is one ugly thing I should say about these is that to setup Tycho you need to understand mvn, osgi and P2 - and that is a challenge...but the same challenge also existed with PDE/Build and the power of tycho is that because it is much more strict it actually helped us to cleanup things we ignored or didnt realize was true problems for p2/osgi until Tycho told us differently.\n
  • #128 ...but time is short and its time to try and sum up what is good, bad and ugly about Tycho &lt;click&gt;. The good is that this stuff just works - the additional metadata is concise and opens up to use all the great stuff happening in the mvn ecosystem. And something I haven&amp;#x2019;t highlighted here is that the guys from sonatype and SAP and others are very active on the mailing list to help figure out the tricky corners and fix bugs you helped identify. The Bad side is that there are bugs and there have been some nasty ones but luckily most of these are fixed in 0.13 and onwards and I hope at tonight BOF&amp;#x2019;s we can tackle some of the left over issues&amp;#x2026; and if there is one ugly thing I should say about these is that to setup Tycho you need to understand mvn, osgi and P2 - and that is a challenge...but the same challenge also existed with PDE/Build and the power of tycho is that because it is much more strict it actually helped us to cleanup things we ignored or didnt realize was true problems for p2/osgi until Tycho told us differently.\n
  • #129 ...so in overall Tycho is mostly just damn good :)\n
  • #130 ...so in overall Tycho is mostly just damn good :)\n
  • #131 ...and that actually concludes my talk and I&amp;#x2019;ve put some resource links here to what I&amp;#x2019;ve used to track/learn tycho and also the blog I&amp;#x2019;ve written about our tycho versions plugin for those that are interested...and with that I open up for questions.\n
  • #132 ...and that actually concludes my talk and I&amp;#x2019;ve put some resource links here to what I&amp;#x2019;ve used to track/learn tycho and also the blog I&amp;#x2019;ve written about our tycho versions plugin for those that are interested...and with that I open up for questions.\n
  • #133 ...and that actually concludes my talk and I&amp;#x2019;ve put some resource links here to what I&amp;#x2019;ve used to track/learn tycho and also the blog I&amp;#x2019;ve written about our tycho versions plugin for those that are interested...and with that I open up for questions.\n
  • #134 ...and that actually concludes my talk and I&amp;#x2019;ve put some resource links here to what I&amp;#x2019;ve used to track/learn tycho and also the blog I&amp;#x2019;ve written about our tycho versions plugin for those that are interested...and with that I open up for questions.\n
  • #135 ...and that actually concludes my talk and I&amp;#x2019;ve put some resource links here to what I&amp;#x2019;ve used to track/learn tycho and also the blog I&amp;#x2019;ve written about our tycho versions plugin for those that are interested...and with that I open up for questions.\n
  • #136 ...and that actually concludes my talk and I&amp;#x2019;ve put some resource links here to what I&amp;#x2019;ve used to track/learn tycho and also the blog I&amp;#x2019;ve written about our tycho versions plugin for those that are interested...and with that I open up for questions.\n
  • #137 ...and that actually concludes my talk and I&amp;#x2019;ve put some resource links here to what I&amp;#x2019;ve used to track/learn tycho and also the blog I&amp;#x2019;ve written about our tycho versions plugin for those that are interested...and with that I open up for questions.\n
  • #138 Thank you - and Please go to this URL to vote on this talk! thank you!\n
  • #139 Thank you - and Please go to this URL to vote on this talk! thank you!\n
  • #140 Thank you - and Please go to this URL to vote on this talk! thank you!\n
  • #141 Thank you - and Please go to this URL to vote on this talk! thank you!\n
  • #142 Thank you - and Please go to this URL to vote on this talk! thank you!\n
  • #143 Thank you - and Please go to this URL to vote on this talk! thank you!\n
  • #144 Thank you - and Please go to this URL to vote on this talk! thank you!\n