On 21/10/2007, Olaf Bergner <[EMAIL PROTECTED]> wrote: > > Thank you, Stuart, for your instant reaction. On a related note: wouldn't > it > be a good idea if the maven-bundle-plugin verified the correctness of the > manifest it produced, reported any errors it produced and failed the build > if need be.
sure - that's a good idea, would you mind raising it as an improvement on JIRA? https://issues.apache.org/jira/browse/FELIX/component/12311143 Maybe it's just me - I certainly often do get that impression in > the face of most of the problems I encounter - but invalid manifests gave > me > a lot of trouble. What's so aggravating is that these problems are usually > easy to fix but a little tricky to diagnose, especially if you haven't yet > been bitten by them. > > Cheers, > Olaf > > > -----Ursprüngliche Nachricht----- > > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Stuart > > McCulloch > > Gesendet: Sonntag, 21. Oktober 2007 10:15 > > An: [email protected] > > Betreff: Re: [maven-bundle-plugin] Linebreaks in description element can > > lead to invalid manifest header > > > > On 17/10/2007, Stuart McCulloch <[EMAIL PROTECTED]> wrote: > > > > > > 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. > > > > > > > > FYI, I've fixed the description problem in trunk under the following > > issue: > > > > https://issues.apache.org/jira/browse/FELIX-403 > > > > the Include-Resource problem was already fixed in the latest snapshot > > > > -- > > Cheers, Stuart > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
