cancel
Showing results for 
Search instead for 
Did you mean: 

OSGI-Build is failing

bernd_ruecker
Champ in-the-making
Champ in-the-making
In the current trunk the OSGI build is failing on my local machine:


     [exec] [INFO] ————————————————————————
     [exec] [ERROR] BUILD FAILURE
     [exec] [INFO] ————————————————————————
     [exec] [INFO] Compilation failure
     [exec] C:\Projekte_Activiti\activiti\modules\activiti-osgi\src\main\java\org\activiti\osgi\Activator.java:[22,21] package sun.tools.java does not exist
     [exec]
     [exec]
     [exec]
     [exec] C:\Projekte_Activiti\activiti\modules\activiti-osgi\src\main\java\org\activiti\osgi\Activator.java:[22,21] package sun.tools.java does not exist

May Java Version:

java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)

Can anybody take care of this?

Thanks
Bernd
4 REPLIES 4

tombaeyens
Champ in-the-making
Champ in-the-making
also other people reported problems with the eclipse maven integration with the bundle packaging type.

Guillaume,
Would it be possible to move OSGi capabilities in the activiti-osgi module?  Maybe that one could be the bundle that includes all the other activiti libs/classes…
It would give me a more comfortable feeling if we keep the packaging of the engine modules as jar.  And only do OSGi stuff in the osgi module.

WDYT?

gnodet
Champ in-the-making
Champ in-the-making
Seems the build issue has been fixed.
I'll see what I can do for the OSGi metadata and I see two solutions:
   * do not use the OSGi bundle packaging and just use the plugin to generate the manifest
   * keep activiti-engine a plain jar and embed it in activiti-osgi
Though, i've been working on osgi projects using maven-bundle-plugin for quite some time now and haven't had much feedback on such problems.  What kind of problem are there exactly?

jbarrez
Star Contributor
Star Contributor
Dave Syer tried to do a fresh import and got many error in STS.

However, after changing the bundle to jar, he could import it.
Reverting it again to bundle afterwards didnt create any problems, how odd it may seem.

gnodet
Champ in-the-making
Champ in-the-making
Ok, then I'll try to use the maven-bundle-plugin to generate the manifest but keep the jar packaging.