2008/9/17 Sahoo <[EMAIL PROTECTED]> > Stuart, > Stuart McCulloch wrote: > >> 2008/9/16 Sahoo <[EMAIL PROTECTED]> >> >> >> >>> I had sent this email to maven forum, but I think I may be able to get >>> some >>> tips from felix forum as well because I am using maven-bundle-plugin. I >>> must >>> say I am surprised as to how this is happening when I am using manifest >>> goal >>> of bundle plugin. Any help is much appreciated. >>> >> >> is this an intermittent/random problem or is there a pattern, >> > Kind of random problem, so it makes it that much more difficult. I am > trying to find out a pattern. If I do find a pattern, I shall let you know. > >> like same >> platform / JVM? >> >> > We have only seen it on Solaris systems with different versions with > different Sun JDK releases like 1.5.0_12 and1.5.0_16. > >> does it only happen when building the full tree from the top, or just >> building that project? >> >> > Only when building full tree from top. > >> personally I wasn't able to recreate it locally, there were no spurious >> classes in the jar. >> >> > You wrote your own test case, right? I must say there are some other > artifacts in that same reactor that use same kind of pom, but they don't > face the problem. It's consistently this particular artifact. >
actually I used the latest GlassFish build, but trimmed the reactor down to the relevant artifacts - I'll try the full tree > > I'll need to look at the jar-plugin to see how such content could make it >> in >> as BND isn't >> involved, so more info about when/where this bug happens would be >> useful... >> >> > maven-bundle-plugin's manifest goal is only involved in making the > manifest. > > Thanks and regards, > Sahoo > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Cheers, Stuart
