Just a number of pointers on the debugging, testing and deployment of OSGi applications ... Debugging Debugging is often an essential activity if the application just does not want to work as it is supposed to. Eclipse offers strong support for debugging of OSGi applications through the Plug-In Development Environment (PDE)
To get eclipse PDE working hand in hand with Maven is a rather tricky task. I have already written about some necessary tweaks to get it working. Another way is to use the Apache Felix Maven bundle plugin. This Maven plugin is able to generate the necessary files for the
Problem Maven uploads work fine using the normal goal deploy:deploy, but when using deploy:deploy-file it seems like the authentication information in the settings.xml is ignored. So, it is not possible to upload to a Nexus repository, which requires password authentication for upload of artifacts. mvn deploy:deploy-file
The Problem Some libraries like XStream or Beans serialization require direct access to the classloader of the bundles, which use them. These libraries need access the classes, in order to deserialze them. Otherwise expections like the one below occur: SCHWERWIEGEND: Application class de.mxro.textedit.gdocseditor.gui.GoogleDocsEditorGUIApp failed to
The Problem I have created a very simple Swing class, which is to be started by an OSGi Declarative Service. public class SwingOSGiApplicationService implements ApplicationService { public void activate() { System.out.println("Starting Application Service; show window"); Runnable launcher = new Runnable() { @Override public void run() { JFrame aWindow = new JFrame(
Although it is quite easy to generate OBR meta data for Maven deployments, the general tool support for OBR seems to be quire weak. Links Presentation at eclipsecon 2007 (Abstract) Webpage describing the plugin from above presentation Bundle Plugin for Maven (with additional goals to create bundle meta data)
Abstract: It is no secret that end user interfaces are not Java‘s strongest point especially on the desktop. Nonetheless, there is a great choice of interesting frameworks, some of which are listed below. Links: Generate GUI from Java beans Metawidget http://metawidget.sourceforge.net/videos.html GWTSwing An attempt
The Problem Maven has a slightly different approach to handling resources in Java packages than Eclipse PDE. For Maven, usually only *.java files are compiled and the rest of the files in java packages are ignored. For Eclipse PDE, these files are included in the classpath. This works fine as
General Guidelines * Use the same version number for the bundles and Maven artifacts for releases * For snapshots, append .SNAPSHOT for the bundle version and -SNAPSHOT for Maven (E.g. Bundle: 0.0.1.SNAPSHOT, Artifact: 0.0.1-SNAPSHOT) * Use the same name for bundle name and artifact ID * When a
Eclipse PDE and Maven do not always work together seamlessly. Here a few links that can be of help: (for more help also have a look at the Maven/OSGi tutorials) Mails PDE dependency and Maven dependency Open Bug for M2Eclipse And another open bug for M2Eclipse Wiki page of
This post contains a number of experiences made while making a Swing desktop application modular using Maven and Subversion. Environment Install a subversion server (for instance on ubuntu server or on windows using VisualSVN) Set up one subversion repository for all your projects. (Read more on setting up SVN repository
Maven and subversion both manage different versions of development projects but they have different focusses. While Maven focusses on the management of whole modules/projects/packages, subversion manages each and every file of the development. In Maven, the version that is currently under development is annotated with the version postfix
