Brian, that works too. But most of the time, you've got several
projects that all need the same collection of jars, so you end up
installing this pom by itself and then you can add it to any project
at any time.
Wayne
On 7/20/07, Lalor, Brian <[EMAIL PROTECTED]> wrote:
Wayne gave me more credit than I deserved, but we weren't quite talking about
the same thing. Forget putting anything directly into the repository.
Instead, assuming you're using a multi-module project, create a new sub-module
and define your dependencies there.
So, your tree would look something like this:
. top-level dir ("/"; groupId: com.foo, artifactId: top-level)
|- pom.xml
|- big-ass-dependency (groupId: com.foo, artifactId: big-ass-dependency)
| `- pom.xml
|- web-proj
`- pom.xml
In /big-ass-dependency/pom.xml, you'd specify your dependencies. In
/web-proj/pom.xml, you'd declare your dependency on big-ass-dependency:
<dependency>
<groupId>com.foo</groupId>
<artifactId>big-ass-dependency</artifactId>
</dependency>
I'd like to model this in maven just for my own edification, but I don't have
time right now. :-(
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 20, 2007 10:35 AM
> To: Maven Users List
> Subject: Re: Large number of dependencies
>
> It did not work, but pehaps I'm doing something wrong,
> because it still
> wants a jar. I added an appropriately named "empty jar"
> (manifest only)
> and even tried putting the pom in the jar.
>
> For now, I must put it on the back burner and deal with
> production issues
> (this counts as R&D).
>
> Thanks anyway for taking the time to answer.
> "Wayne Fay" <[EMAIL PROTECTED]> wrote on 07/20/2007 10:09:01 AM:
>
> > Yes, that works. Create a pom with no code, packaging pom, and then
> > <depend> on that pom in your real code project. It should bring all
> > the dependencies along with it.
> >
> > Wayne
> >
> > On 7/20/07, Lalor, Brian <[EMAIL PROTECTED]> wrote:
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]
> > > > Sent: Friday, July 20, 2007 9:20 AM
> > > > To: users@maven.apache.org
> > > > Subject: Large number of dependencies
> > > >
> > > > I'd like to bundle them into a sort of "dependency group"
> > > > that would then
> > > > take only one entry in my POMs. Suggestions?
> > >
> > > Dunno if this would work, but could you just create a .pom file in
> > your repository without an associated JAR and declare the
> > dependencies in there? Then you'd declare each project's dependency
> > on that single entity.
> > >
> > >
> ---------------------------------------------------------------------
> > > 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]
> >
>
---------------------------------------------------------------------
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]
