Re: maven-bundle-plugin goal manifest - where the manifest is written

On 5/4/2010 9:47 PM, Marshall Schor wrote: > According to the doc > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html , > when you use the goal "manifest", this causes a manifest to be generated > and written to > >${project.build.outputDirectory}/META-INF/MANIFEST.MF. >

maven-bundle-plugin goal manifest - where the manifest is written

According to the doc http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html , when you use the goal "manifest", this causes a manifest to be generated and written to ${project.build.outputDirectory}/META-INF/MANIFEST.MF. But when I tried (version 2.0.1 of the plugin), I found i

Re: Problems with startup order in Karaf

Hello Guillaume, What you are describing is what I want to be included in camel, preferably in camel-osgi. In my case I'm making it possible to get the possibility to wait until required bundles are started. This is of course a temporary workaround until the Camel team improves Camel's OSGI suppor

Re: Problems with startup order in Karaf

Sorry to not have been clear enough. What I had in mind was that the extender would listen for bundle containing camel components. For each component found into a bundle, the extender would register an OSGI service with a property identifying the name of the component. The object itself would not

Re: Problems with startup order in Karaf

Guillaume, I've now tried the approach using the extender pattern. I did it using iPOJO. Here is the sample code: @Component(public_factory = false, propagation = true) @Extender(extension = "Bundle-SymbolicName", onArrival = "onArrival", onDeparture = "onDeparture") public class CamelExtenderSer

Re: Execution Environment

On 5/4/10 13:54, Guillaume Nodet wrote: I don't think so, the problem is more in felix imho. But karaf will set it anyway in the config.properties. Ok, great. I'll stick to my original solution then... -> richard On Tue, May 4, 2010 at 18:42, Richard S. Hall wrote: Thanks. I just

Re: Execution Environment

I don't think so, the problem is more in felix imho. But karaf will set it anyway in the config.properties. On Tue, May 4, 2010 at 18:42, Richard S. Hall wrote: > Thanks. I just commented on the issue...I was going to address this issue > in the framework, but it is not clear if there is also a

Re: Execution Environment

Thanks. I just commented on the issue...I was going to address this issue in the framework, but it is not clear if there is also an issue with respect to Karaf that also needs to be addressed. -> richard On 5/4/10 12:12, Chris Blunck wrote: Ticket opened: https://issues.apache.org/jira/brows

Re: Execution Environment

Ticket opened: https://issues.apache.org/jira/browse/FELIX-2324 -c On Tue, May 4, 2010 at 10:23 AM, Richard S. Hall wrote: > No, Felix doesn't set this automatically. You must specify it on the > command line or in config.properties... > > Howe

Re: JAXB and Apache Felix

Mike check this link http://www.dynamicjava.org/projects/jsr-api/jaxb-osgi Maybe it could be useful. On Tue, May 4, 2010 at 8:54 AM, mjk wrote: > Hey Martin, > > Thanks for the reply. > > I checked the imports in the Felix console, and sure enough there were no > imports for the annotations.  H

Re: Execution Environment

No, Felix doesn't set this automatically. You must specify it on the command line or in config.properties... However, I guess we could set this by default according to the JRE, sort of like we do for JRE packages...if you want to open a JIRA issue for this, I'll look into it. -> richard On

Re: Execution Environment

I don't think Felix Framework sets this property by itself. Equinox seems to do so IIRC. I actaully hit the same problem and I did add the property in the etc/config.properties file, so that the next release will have a J2SE-1.5 by default (which allows to deploy many bundles through OBR). I thin

maven-bundle-plugin usage question - poorly formed package names

I'm trying to create an OSGI bundle that contains transitive dependencies using the maven-bundle-plugin.  However two of my dependencies are poorly formed.  One has a capitalized package name yet code refers to this using lower case.  Another dependency has a space in the package name.  The plugin

Execution Environment

Hello, Please forgive this question in advance if it has been well documented or discussed elsewhere. I failed to find references to it when searching for "execution environment felix" and other searches for how this concept works. I'm familiar with execution environments but I don't understand

Re: JAXB and Apache Felix

Hey Martin, Thanks for the reply. I checked the imports in the Felix console, and sure enough there were no imports for the annotations. However, I still get the same Exception. --Mike On Tue, May 4, 2010 at 12:54 AM, Martin Thelian wrote: > Hi! > > This sounds that you have not defined the I