Creating a target eclipse platform and bundling non-osgi bundles on the fly

One challenge even in eclipse 3.5 is managing the target platform for your eclipse RCP.  It turns out that while many enterprise level bundles are already OSGi ready, many are not. If you want to create a target platform more easily, and have an automated build facility that does not require manual conversion of non-OSGi bundles, you need to create process to build the target platform with your 3rd party bundles.

The idea is very similar to what is described in this blog http://springosgi.googlepages.com/ where a target platform is built for a spring dm (spring dynamic modules) environment. Follow the instructions at http://springosgi.googlepages.com/ch01.html carefully. But the question is, if you have non-OSGi bundles, what do you do? Can you automate the process?

Lets assume that you have a bundle that should be in the target but is not OSGi. I’ll use miglayout-3.7-swt.jar as an example.

Prepare Your Eclipse Environment

Install m2eclipse, http://docs.codehaus.org/display/M2ECLIPSE/Home.

This will implement the maven functionality to manage dependencies. This should have be installed if you followed the instructions on the blog.

Enhance Your pom.xml

First, add  the following repository to your pom file:

   1: <repository>
   2:     <id>com.springsource.repository.bundles.milestone</id>
   3:     <name>SpringSource Enterprise Bundle Repository</name>
   4:     <url>http://repository.springsource.com/maven/bundles/mileston</url>
   5: </repository>

Then add the following plugin to your pom.xml:



   1: <plugin>
   2:                 <groupId>com.springsource.bundlor</groupId>
   3:                 <artifactId>com.springsource.bundlor.maven</artifactId>
   4:                 <version>1.0.0.M2</version>
   5:                 <executions>
   6:  
   7: ...multiple executions to transform the bundles using bundlor...
   8:  
   9:                 <executions>
  10:  
  11: </plugin

And within that plugin definition, you can have multiple execution entries:



   1: <execution>
   2:                         <id>miglayout</id>
   3:                         <phase>package</phase>
   4:                         <goals>
   5:                             <goal>transform</goal>
   6:                         </goals>
   7:                         <configuration>
   8:                             <failOnWarnings>false</failOnWarnings>
   9:                             <removeNullHeaders>true</removeNullHeaders>
  10:                             <bundlePath>jars/miglayout-3.7-swt.jar</bundlePath>
  11:                             <packagings><packaging>pom</packaging></packagings>
  12:                             <outputBundle>target/${project.artifactId}.miglayout.3.7.swt.jar</outputBundle>
  13:                             <manifestTemplatePath>${basedir}/template.mf</manifestTemplatePath>
  14:                             <manifestHeaders><![CDATA[Bundle-Name: Miginfocom SWT
  15: Built-By: org.you
  16: Bundle-SymbolicName: net.miginfocom.swt
  17: Bundle-Version: 3.7.0
  18: ]]></manifestHeaders>
  19:                         </configuration>
  20:                     </execution>

Here we have assumed that the folder called jars holds the non-OSGi jars. Maven could also download those to the jars directory as well but you could just copy them to that special directory.


You’ll need a template.mf as well and it will find the default although I set it explicitly in the pom.xml. Don’t forget that the template is extremely sensitive to spaces after the colons (:), you need to have a space.



   1: Excluded-Exports: 
   2:  *.internal*
   3: Import-Template: 
   4:  *;resolution:=optional
   5: Unversioned-Imports:  
   6:  *

Run Maven Packaging


The use the right mouse button context menu to RunAs: Maven Packaging. This builds your target definition. Don’t forget to reload the target platform definition in Windows>Preferences>PDE>Target Platform to ensure that it has all the plugins that were downloaded or were created. You can also stick in other headers inside the POM for the manifest, such as Eclipse-BuddyPolicy: Registered.

Comments

Post a Comment

Popular posts from this blog

quick note on scala.js, react hooks, monix, auth

quick note on scala.js, react hooks, monix, auth Reactjs hooks finally came out of preview in a recent version of React. scalajs-reaction has had support for hooks since they were in preview. React hooks seem like the hot new thing but for me the question is, do hooks help improve your code by improving maintainability, time to market, TCO, etc.? Let’s take a look using authentication as an example and employ monix , a reactive observable framework that also builds on cats . We will assume we are building a SPA. Does it improve your code and make your application & development experience better? Auth Auth processing can be complex. Many react auth examples you find in blogs like to show how to use “react-routing” and “auth” as a switch that determines which routes are protected or unprotected. Protected routes show application specific data. Unprotected routes show login content . Based on storing a “User” object in the browser session/local storage, th...
Read more

zio environment and modules pattern: zio, scala.js, react, query management

zio environment and modules pattern: zio, scala.js, react, query management This blog covers a zio-based fetch design for scala.js, react web applications. It heavily uses the zio “environment” feature to help motivate a point of view on the modules pattern in effect systems. At the end, I summarize some thoughts on ergonomics and complexity. This blog assumes a basic knowledge of zio and react. scala.js is just like scala so you mostly already know scala.js. This blog is a follow-on to previous blogs: https://appddeevvmeanderings.blogspot.com/2019/10/scalajs-react-fetcher-hook_48.html and https://appddeevvmeanderings.blogspot.com/2019/11/scalajs-and-react-suspense.html . I have been keeping an eye on and culling ideas from typscript/javascript fetching libraries that address query management concerns. The formulation below incorporates some of those concerns but does not try to comprehensively duplicate well established javascript libraries. I only care about ...
Read more

attributes with react and typescript.md

If you use typescript with react you may wonder what the right signature is for your “properties” interface. Obviously, your component will have few to many specific properties that reflect your domain. However, you may wish to also provide for the ability to add other attributes, such as those valid for a div property. In other words, you want to extend your props interface with that of the properties from a div element. How do you do that? There are really two issues: How do you extend your props interfaces How do you filter the props once you receive them to just those that apply. Extend Your Prop Interface or Use Sum Types It’s not uncommon to see interface Props { className ? : string yourProp ? : number } with the idea of using it in class MyComponent extends React.Component<Props, any> somewhere. If your component will have an outer div, you may also pass in a react element so that its configurable. But let’s say your outer element is a div and you wan...
Read more