Re: Bad BundleSymbolicName in generated Manifest

2013-12-12 Thread Stuart McCulloch
On 12 Dec 2013, at 08:56, Ferry Huberts wrote: > I just tried it in the latest bndtools, which uses bnd latest (2.3) and there > it works ok. > >> Bundle-SymbolicName: >> org.energy-home.jemma.osgi.ah.zigbee.appliances.generic.long.name.that.will.really.wrap.in.the.manifest;singleton:=true >

Re: Bad BundleSymbolicName in generated Manifest

2013-12-12 Thread Ferry Huberts
I just tried it in the latest bndtools, which uses bnd latest (2.3) and there it works ok. Bundle-SymbolicName: org.energy-home.jemma.osgi.ah.zigbee.appliances.generic.long.name.that.will.really.wrap.in.the.manifest;singleton:=true results in Bundle-SymbolicName: org.energy-home.jemma.osgi

Re: Bad BundleSymbolicName in generated Manifest

2013-12-12 Thread Ivan Grimaldi
Hi, thanks for your reply, but if you look more carefully at the examplke I provided, you'll see that the problem is not that the symbolic name is equal to the artifactId (I want it to be like this). The generated symbolic name is being splitted in two lines with an invalid second line containi

Re: Bad BundleSymbolicName in generated Manifest

2013-12-11 Thread Chetan Mehrotra
Have a look at Maven Bundle Plugin docs around how it computes the Bundle-SymbolicName by default [1]. So in your case it defaults to artifactId (see point 4 under ) Chetan Mehrotra [1] http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html#ApacheFelixMavenBundlePlugin%28BND%29-De

Bad BundleSymbolicName in generated Manifest

2013-12-09 Thread Ivan Grimaldi
Hi, I'm experiencing a problem using felix bundle plugin v2.4.0 and maven v3.1.1: the generated manifest for project with long names contains invalid entry for BundleSimbolicName like: Bundle-SymbolicName: org.energy-home.jemma.osgi.ah.zigbee.appliances.generic;singleton:=true eric It is p