On 12/09/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Stuart McCulloch schrieb: > > the bundleplugin uses standard maven calls to get transitive > dependencies > > so I'll need your complete POM to find out why it's not found (ie. it > could > > be > > a scoping issue) > > it is quite a lot of dependencies (some of them internal), so it would > be difficult for you to reproduce it. so i am trying to find the > dependency which makes problems. to be quicker i tried to use the goal > org.apache.felix:maven-bundle-plugin:manifest, so i get directly to the > MANIFEST.MF. > > though, when trying out this goal, i get a different MANIFEST.MF as with > goal org.apache.felix:maven-bundle-plugin:bundle. is that correct? if > so, i will need to go the longer way with building the complete bundle > and have look inside the jar...
it is certainly possible, depending what part of the maven build phase the manifest goal executes (as it needs either classes or a jarfile to analyze). the manifest goal also doesn't do any embedding, etc. as it's meant to be used to generate OSGi metadata for existing (non-OSGi) maven artifacts, so you'll also see a difference there... -- > manuel aldana > [EMAIL PROTECTED] > homepage: www.aldana-online.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
