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.
I wonder whether this warrants a bug report, i.e. 'Remove linebreaks in those elements that are copied to the generated manifest file'? Cheers, Olaf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
