On 17/10/2007, Olaf Bergner <[EMAIL PROTECTED]> wrote: > > Sometimes I left a perfectly running build to do some cosmetic work in the > projects that produce my osgi wrapper bundles for external libraries, > using > the maven-bundle-plugin. Getting back to the real stuff I fired up maven > only to see my build fail with a compilation error, although I didn't > touch > any 'real' code. Eventually, I found out that the compilation failure was > caused by an invalid header in one of my osgi wrapper bundle's manifest > file. It turns out that the maven-bundle-plugin copies the 'description' > section from the pom into the generated MANIFEST.MF. So that description > better be on one line. If you are like me and habitually format each and > every file before saving - strg-shift-F in eclipse - that restriction > easily > gets violated. I therefore made it a habit to include the description in a > CDATA-section. Same goes for the 'Include-Resource' instruction.
Hi Olaf - which version of the bundleplugin are you using? the latest code in 1.1.0-SNAPSHOT should already handle and fix line breaks in Include-Resource, although I'm not sure if it also fixes the description field. I wonder whether this warrants a bug report, i.e. 'Remove linebreaks in > those elements that are copied to the generated manifest file'? if you can recreate this using the 1.1.0-SNAPSHOT build from apache-snapshots (or build the plugin from source) then please open an issue on JIRA and attach your example POM Cheers, > Olaf > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
