The way Maven is intended to work currently in this regard is that anything that aggregates other projects or dependencies doesn't use the packaging, but instead produces it as an associated artifact. So, if packaging = pom, you get the desired result in terms of the dependency mechanism, but you can still produce an assembly (jar/zip/rpm) from that.
Hope this helps. This is definitely one of the main use cases that needs some polishing up before final release. Cheers, Brett On 9/14/05, Andrew Niefer <[EMAIL PROTECTED]> wrote: > > The resulting artifact of a project A is a directory containing jar files, > binaries and resources and I package this in a jar, or even a zip or rpm > (if I had such a packaging plugin) > > A jar/zip/rpm > - nested1.jar > - nested2.jar > - resources/binaries > - META-INF/manifest.mf > > manifest.mf is an OSGI manifest that specifies nested1.jar and nested2.jar > using the Bundle-ClassPath. > > Consider now another project B that has a dependency on A. When building > B, I don't want its classpath to contain A, but instead I want it to > contain nested1.jar and nested2.jar. > > Is it possible to nest jars this way? Or would something like this require > a custom process-resources plugin? > > -Andrew > > >
