Posts

Showing posts from January, 2011

Two Eclipse p2 repository operations to make you happy

On the integrations side of the Eclipse business I often happen to need two things: 1. add a random OSGi jar to repository 2. copy from one repository to another Looking thru p2 manual it's not always entirely obvious how to do it, so here goes my take on the subject. All my automation uses Ant, so I'll speak a bit of Ant now: 1. Add a random OSGi jar to repository <p2.publish.featuresAndBundles repository="file:/path/to/destination/repository" e.g. ${buildDirectory}/repo publishArtifacts="true" compress="true" append="true" source="/absolute/path/to/folder/with/jar" /> Few notes: 1. source attribute must be an absolute path. 2. source path must contain "features" and "plugins" directories. So if you have only one bundle, make sure to put it under plugins dir first. 3. make sure repository attribute is a URL, not plain path 2. Copy from one repository to another <p2.mirror verbose=&quo

Extending Eclipse Orion

Image
Yesterday Eclipse E4 team announced Orion - an experimental Eclipse Web IDE. There's plenty of information about the project on Orion wiki . Orion is a set of JavaScript and HTTP APIs that simplify common development part of rich applications, like file storage, preferences, authentication, dialogs, selection. Since it's coming from Eclipse, Orion is skewed towards IDE development, so from start it also includes text editor with some decent features, like JavaScript syntax highlighting and JSLint integration. The project may go towards strengthening it's JS IDE feature set, as well as enhancing it's core side - extensibility, client APIs ...or do it all at once. In any case it's going to be fascinating journey! So how to extend Orion? One can re-implement existing HTTP API in language other than Java; add more HTTP APIs, e.g. for task management, calendar, etc. Same with JavaScript API - it seems fairly easy to add more. Looking at this from classic Eclipse adopter