I'll certainly need the structure, so I'll have a deeper look into the
project info reports plugin and archiva.
Thanks Brett,
Mark
On 25/09/06, Brett Porter <[EMAIL PROTECTED]> wrote:
If you need the structure, yes. It would be good to factor out into a
common component - currently we use this from archiva via the project
info reports plugin.
If you just need the full list, ${project.artifacts} works.
- Brett
On 25/09/2006, at 10:04 PM, Mark Hobson wrote:
> Hi there,
>
> Just looking at MPH-14, since we've needed this for a while, and
> hoping someone could give me a point in the right direction. What's
> the best way of obtaining the dependency tree? From an injected
> MavenProject I can obtain the immediate dependencies, but what's the
> correct way of obtaining their dependencies? Should I be using
> artifacts instead?
>
> Can't find much documentation on the model and what @components are
> available for this kind of thing. I've looked at the
> DependenciesReport and it looks like it takes a rather complex route
> to obtain this info - is this the best way?
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> 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]
