I think he was expecting that his "produced JAR" would have all the other 100 jars (that he depended upon transitively) bundled inside it.
Is that what you want? Or what? Wayne On 5/10/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 5/10/07, lightbulb432 <[EMAIL PROTECTED]> wrote: > How can I create a project for the sole purpose of its pom.xml serving as a > place to organize several dependencies. For example, if I have a main > project that depends on 100 JARs, could I get this main project to depend on > 4-5 subprojects whose sole purpose is to specify a subset of those JARs? > > Then when I go to package or deploy the main project, all 100 JARs are > included. > > How can I make this possible? I tried to have a JAR project depend on a POM > project but this didn't work - the produced JAR came out empty... How big is this module that depends on 100 jars? Could it benefit from being broken up in to multiple modules, each with a smaller set of dependencies? Yes, you can depend on a pom that lists dependencies, and take advantage of Maven's transitive dependency resolution mechanism. Use type=pom in the dependency element. You'll have to explain further what you tried that produced an empty jar. If it wasn't working, I'd expect a compilation error, not an empty jar. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
