Managing your Eclipse Installs

Markus Knauer

EclipseSource

Why Yoxos?

Why OSGi?

Solve scalability and manageability issuesImprove reuse

How?

Devide and conquer (modules)Version (allow for variety)Explicit lifecycle

OSGi == classloading on steroids

Why Yoxos?

Devide and conquer (split up monolithic repositories)

Version (versioned repositories)Explicit Lifecycle

Yoxos == p2 on steroids

Makes it easier to deploy and manage sophisticated applications

TeamSustainabilityPerformanceExtensibility

Team: Share

Tool selection (plugins, versions)

Team: Share

Preferences (e.g. code formatting)

Team: Share

Checkstyle configurations

Team: Share

Mylyn configurations(including queries)

Team: Share

Team project sets==

a selection of projects from your SCM

Team: Share

One click to start a tool chain and get all necessary configurations and

source code

Sustainability

Tool configuration stored in JSON in a file:

.yoxos file

Sustainability

{ "profile": "sliceID":"3.5.2.20101029", "components":[ "org.eclipse.mylyn.java_feature.feature.group", "org.eclipse.jdt.feature.group" ], "configurations":[ { "id":"checkstyle", "configuration":"<csconfig><name>Yoxos ...

Sustainability

Repositories are versioned and immutable

Sustainability

Repository content gets analysed at repository creation time – no

surprises at install time

Sustainability

Tool configurations can be stored together with source code and can

be recreated at any point in the future

Performance

Fast search (DB-backed)

Performance

Fast install (cloud-backed)

Performance

Fast update check (in less than 1 second)

Extensibility

Add your own plugins (and gain all of the Yoxos benefits)

Extensibility

Roll your own „distribution“

Demohttp://eclipsesource.com/yoxos5

Thank you!http://eclipsesource.com/yoxos5