Hi all,
I am trying to distribute OSGi-bases Application using Maven. In best case,
when I distribute the application to other people not using Maven or OSGi,
they just should klick a start.bat and the application should start
including the OSGi-Framework.
At the moment, I am using the Maven-Bu
I ever got each subproject to generate a resource file called
filter.properties in the target directory directly.
If the subproject's name is example, then the resource file has the
following content:
example.build.finalName=${pom.build.finalName}
Then I created a new subproject called resource-f
Hi All,
I am porting a large equinox-based application to run on felix.
Unfortunately I use buddy classloading all over the place, specifically the
dependent buddy policy.
Also, the reason I use buddy classloading instead of DynamicImport * is that
DynamicImport creates some problems for my bu
The bundle org.apache.felix.http.jetty-1.0.0 exports
org.osgi.service.http;version=1.1 but imports
org.osgi.service.http;version=1.2, which caused this problem.
The probable fixing is to remove the hardcoded export version 1.1 of package
org.osgi.service.http from the pom.xml and just let maven-bu
On 6/2/09 3:34 PM, Ted Stockwell wrote:
Hi All,
I am porting a large equinox-based application to run on felix.
Unfortunately I use buddy classloading all over the place, specifically the
dependent buddy policy.
Also, the reason I use buddy classloading instead of DynamicImport * is that
Dynam
5 matches
Mail list logo