2009/4/3 Craig L. Ching <[email protected]> > > yes, sounds like a Maven bug - are you trying to release > > several artifacts in one go? it may be that this only occurs > > in a multi-module release, which would square with another > > bug (MNG-1682) > > > > I'll have a look at that one, yeah, I'm doing a multi-module release. > > > have you tried setting the type of your dependency to be > > bundle? ie. in the "com.mqsoftware.appwise:appwise-core" pom, > > it would look like this: > > > > <dependency> > > <groupId>com.mqsoftware.appwise</groupId> > > <artifactId>appwise-security</artifactId> > > <version>1.0.0.10</version> > > <type>bundle</type> > > </dependency> > > > > this might resolve the problem - alternatively try releasing > > one at a time... > > > Yeah, I tried that but it didn't find the bundle. I *think* it was > looking for a .bundle extension, but I might be misremembering. > > > FWIW we use the bundleplugin internally at Felix and have > > released many artifacts with "bundle" packaging, although > > IIRC they were one at a time > > > I know, I steal most of my maven configuration from Felix and Sling ;-) > > So, if this is a bug, I'm actually thinking of using > maven-bundle-plugin's ability to keep my jar packaging and use the jar > plugin to add the manifest, that should work in theory, right? >
absolutely - several Apache projects do this so they can keep their original packaging > > -- > > Cheers, Stuart > > > > > > Thanks Stuart, I appreciate the help. > > Cheers, > Craig > -- Cheers, Stuart
