Some of the eclipse libraries are not so thightly bound to OSGi and lately I wanted to use EMF in a grails project. It came to me that there are no current maven artifacts available for EMF, so I had to roll my own.
Asking stackoverflow, I first tried to re-jar the bundles with tycho, but that gave me all the OSGI-deps in one jar, what wasn't what I was looking for. After reding through some discussions around maven and p2 in the eclipse bugzilla, I noticed that b3 has the capability to mirror a p2 repository in a maven compliant layout.
As I wanted to use the xsd to ecore converter I created a aggregation for the xsd sdk
notice the maven config at the end of the aggregator tag.
Then I uploaded it to google drive, so that I can consume the repo from heroku build.
One major drawback is, that the source bundles are not maven conformant, so that attaching them automagically won't work.
Today I finished my migration of a (small) demo app to the new Vaadin 8 API. First of all: Vaadin 8 has a compatibility layer. Everything ...
In this tutorial we will put together a full application stack for a multi-tenant architecture. We will be using Vaadin and Vaadin-Sprin...
Vaadin 8 (currently in beta) comes with a whole new DataBinding API that makes heavy use of the Java 8 Lambda Features. Unfortunately Java...