I wrote a plugin for InstallShield to build a "merge module". 1 merge module
represents 1 jar in our case. We then assemble an installer by taking all
merge modules that we need for our application. The merge module should only
bundle the jar that it is directly dependent on, not any jars that this jar
is dependent on (these are put in a different merge module).
regards,
Wim
2005/12/20, Brett Porter <[EMAIL PROTECTED]>:
>
> Can someone provide a reason why this is needed? I can't think of a
> single reason to use it off the top of my head...
>
> - Brett
>
> On 12/21/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
> > >
> > > >> What if I only want the direct deps instead of the transitive ones?
> > > >
> > > > ${project.dependencies} - but these are just model dependencies, not
> > > > artifacts. If you need the artifacts, take the union of this and
> > > > ${project.artifacts}.
> >
> >
> > I think that many plugins use this functionality, so maybe that should
> be
> > moved to the maven core to avoid that this code is duplicated in many
> > places?
> >
> > regards,
> >
> > Wim
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
