Another nice journey with Maven – or how to sign a jar file

Yes I love Maven, for sure. Maven gives you the capability to build project everytime the same and in every environment. I often explain Maven as a brilliant facility manager, who is able to put all the build, test, package and delivery instruments togehter and then build all the stuff according to your building instructions.

But what if I have to sign a JAR file with a code signer certificat? And this certificate is owned by another company, and they will not provide this certifacte to me. How can I setup a project with Maven that let me build and sign the project by a selfsigned certifacte, while my customer other my build server can use the code cert?

First step…

I need a selfsigned code certificat in a keystore. Read the following tutorial on how you can do this Add this keystore now to the project. My keystore is named awfstore

Once we have done this, let the Maven project know that we want to sign the jar file by adding the following snipped to the build section in the pom.xml.


We are using the “maven-jarsigner-plugin”. The configuration is done by some variables, starting with “sign.”. The values for this variables are definied in the properties:


You can build now the project and it will sign your project with the certificat awf from the awfstore. Replace this values, with your values. But how can we achieve that a Buildserver like Jenkins or Atlassian Bamboo can use other values?

Add the following definition to your pom.xml:


This will activate the Profile compSignerKeyStore, which will override the variables with new settings. This settings can be placed in the setting.xml of your Buildserver or of any developer. It can looks like this:


Have fun


Leave a comment

Posted by on November 26, 2015 in Java, OpenNTF, Maven


My slides from SNoUG 2015 – Content is in German

Englisch version is in work and will come soon


Posted by on October 28, 2015 in OpenNTF


Tags: ,

Currently recovering

Dear All,

It’s a while ago, since my last post. The best excuse is, that I really had a lot of projects to push forward and less of time to talk and blog about. But that’s only the half of the story.

Last month, on June 9. I was in Spain for a customer meeting. It was a really good meeting and it was nice to be there. But during the meeting, I was getting cold. Real cold and my first tought was: what a strong air conditioning. But in fact, my body temperature was rising and the cold was a result of the fever. We went to the airport after the meeting, and I realized that also the airport has an air conditioning. After standing a while outside in the warm spanish sun, we took our flight back home. My wife picked me up I had a night with nice fever driven dreams.

The day after, at the evening, we went to the hospital. My right leg was twice thick then my left one, but I was more caring about the high fever and the diarrhea. Fortunately the medical team and the doctors at the hospital didn’t ignore my leg and took the swollen leg at their top priority. According to some swiss hospital rules, I was moved to the isolation station.

A team of medical doctors started to figure out why my leg was so swollen and why all me blood doesn’t look really good. They started with a antibiotics therapy, which had a strong impact to the fever. Day by day the size of the leg was shrinking, but the heavily forced skin has built some bubbles, which were filled with some liquid. A part of the medial team where really excited about this fact, because the took some of the liquid from the bubble and could analyze what was happened to my leg (It was fun to see what passion these doctors had, because of this bubble and the opportunity to know more).

Flesh eating bacteria! What a radical diagnose. I heard also the “normal” and the worst case scenario of this disease. To be honest, in the worst case, I wouldn’t be able to write this blog entry. I wanna thank first god the almighty father and creator of heaven and earth, for my recovery, for his carrying, for all the moments where I could feel his presence and for pointing me to this wonderful song which gave me hope and patient ( Thanks to all friends who prayed for me. Thanks to the medical team and the doctors at KSW Winterthur, you did a great job. And thanks to my company, who is giving me the time to recover and handles all my projects. And last but not least to my family, thanks for every visit, SMS and your prayers: I love you!

My leg ist recovering. Fever is gone, but the skin of my leg has still the nice color scale from a bright orange to a dark yellow. But the skin is also recovering and I’m able to type and think. My action circle is currently my home and I will remain at home, until my leg is recovered. It’s hard to stay at home and not enjoy the swimming or other outdoor activities, but patient is the best friend currently.

I hope that I can now catchup with all the interesting projects I was involved and a lot of news around XPages, Java and some new technologies.

All the best


PS: Sorry Bruce that I missed your birthday, be blessed!


Posted by on July 6, 2015 in OpenNTF


#IBMNotes25 Party – can’t wait….


Leave a comment

Posted by on January 20, 2015 in OpenNTF



Maven and XPages Plugin – From Scratch / Part IV The feature

While Switzerland was covered with snow, the OpenNTF Base project has made some progress. There are two new plugins, one is org.openntf.base and the other is org.openntf.base.lib.internal.

org.openntf.base contains all the stuff to register the plugin collection as an extension library and also all “Top Level” classes. org.openntf.base is designed to have all the dependencies to the XPages engine. I try to make org.openntf.base.jaxb.dxl with less dependencies to other plugins, as possible. specially not any dependency to the XPages Engine (as I sad, I TRY). My intention is to reuse the org.openntf.base.jaxb.dxl part also for Notes Client plugins.

org.openntf.base.lib.internal contains all the JAR files which will be used in the org.openntf.base package, but not exposed to the Desinger Client. Maybe there will be a org.openntf.base.lib.external plugin, which contains jars of useful java libraries, that could also be used at the Designer Client level. GSON and GUAVA are candidates for this.

Btw. the org.openntf.base.jaxb.dxl.testsuite is also moved to org.openntf.base.testsuite and is now a fragment of org.openntf.base

Ready for the next move? ….. we need a feature to bring all the plugins under one umbrella. (Btw. the testsuite Fragment will not be part of this feature!)

It all begins with a new ………. module!


And the packaging type of this plugin is “eclipse-feature”221

Once we have the new project, we need to files:

  • feature.xml
  • build.properties222 223

Lets open feature.xml and fill the following stuff into the editor:224

On the plugins tab, please add all the plugins you need225

And on the information tab, please fill at least the Copyright Notice. Without it, you wouldn’t belive, but the feature is not loaded in the Designer Client.226

And on the build tab, please select feature.xml227

Check if everything is fine with your run configuration “clean install”

Leave a comment

Posted by on December 31, 2014 in Java, Maven, OpenNTF, XPages



Maven and the magic of profiles

Maven and the magic of profiles

POI4XPages has a module called poi.assembly. This module builds the final ZIP file which can be uploaded to the OpenNTF website. One step in the assembly is that the module downloads the source code direct from github. This step takes a lot of time, so each mvn clean build takes a lot of time, because the assembly line is also executed. Fortunately Maven has a concept called profiles. Maven let you define different profiles. In the POI4XPages case, I’ve built two different profiles, which contains different set of modules:

200Each profile has its own id tag. The default_no_assembly profile is activated by default. The <activation> markup let you activate also profile by defining environment variables.

I’ve now to different run configuration in my eclipse client. To run the default profile, I use the following:


But if I need the assembly profile, I use the following configuration:


Merry christmas!

Leave a comment

Posted by on December 24, 2014 in Architektur, Java, Maven, OpenNTF, POI4XPages, XPages



Maven and XPages Plugin – From Scratch / Part III – The Testsuite

Part I has covered the building of the parent pom.xml, Part II was about the plugin and now in Part III we talk about the test suite. It’s fair to say that this part seems not to be very interesting, but in this Part we talk also about the why.

Why do I make the org.openntf.base.jaxb.dxl plugin?

The core purpose of the jaxb.dxl plugin is to convert a DXL export of a document, or of some design elements into an object based representation. Imagine this: You have a document with 2 rich text fields, one is a traditional rich text field and the other is mime based. For some reason (like transforming the content of the rich text field to a POI document or PDF document) there is an interest in the structure of this rich text field. A simple export as DXL and conversion to this java objects which are cascaded helps a lot.

Or you have this database, and you want to scan the content of all design element for a specific @Formula….. Export the database to DXL and convert it with jaxb to java object tree. And the scan the tree and analyse.

But why not start with the implementation, that sound better than testing!

Agree. Implementing is always better than writing test for the sake of writing tests. But after reading the book “Test Driven Developement” by Kent Beck, my understanding of test has changed. Tests explains what I want to do. Read the following test:


This test covers my user story “Reading a dxl-document.xml and convert it to a java object structure”. To make this test work, I’ve to writte a lot of implementation stuff, so stay tuned.

The next Maven module -> org.openntf.base.jaxb.dxl.testsuite

Again with the eclipse client:


select as packaging type “eclipse-test-plugin”:

152And we have a new project.

And now repeat the following steps, like you have done for the plugin in Part II

  1. New file called MANIFEST.MF into the folder META-INF
  2. New file called

Open the MANIFEST.MF File and go to the MANIFEST.MF Tab and enter the following stuff:

153The directive “Fragment-Host” makes this plugin to a fragment of org.openntf.base.jaxb.dxl. This is the best behavior to separate test and implementation in a plugin.

Open the File and go to the tab. Enter the following stuff:

154Now is a good moment to do a right-click on the project go to Plugin-Tools and execute “Update Classpath”

Open the MANIFEST.MF again and add the following dependency. This is needed that we can start writing our test class.


Let’s write the first Test:


We have also imported the dxl-db-test.xml and the dxl-document-test.xml. This documents were produced by a nice simple DXL Export.

To make the test compile (STEP 2 in TDD), we have to import the XSD File for domino_9_0_1 and convert it to classes. We use for this the JAXB import

JAXB Import of the domino xsd


Start with menu “New” and select the JAXB Classes from Schema Wizard


Select the target project for the import (yes our plugin)


If you do not have the domino_9_0_1.xsd in a project in your workspace, you can import it from your Notes/Data directory


Please specify carefully the package, where the classes should be produced. Existing classes will be overwritten (note to myself, move the DXLActivator Class to an other package or a level up)164

Select finish. The import will now generate a lot of classes.

You can now resolve the import of the Document object (yes its a …jaxb.dxl.Document object)


Time to finish the compilation problems in the test class.

Create the ConvertorFactor in the plugin (see the package that I select? It’s outside of the dxl package, because the content of this package was generated before).


We build also a dummy implementation of “convert2DocumentFromStream”. 167

Only one step, and we can test (with executing our runtime configuration)

We have to include the *.xml Files in our binary build. We open for this step the MANIFEST.MF and add the 2 files


Lets build the project by executing org.openntf.base clean install169

Oh yes the build fails! This is total ok at this point, because our test fails, and a failing test should stop our build!

Now its time to have some fun and finalize the plugin… The next Part will cover how to build the feature and the update site

If you wanna follow the project, please watch this repository on

Leave a comment

Posted by on December 23, 2014 in Architektur, Java, Maven, XPages


Tags: ,


Get every new post delivered to your Inbox.

Join 872 other followers