On 07/11/06, Brett Porter <[EMAIL PROTECTED]> wrote:
MNG for now - thanks!
Done: http://jira.codehaus.org/browse/MNG-2654
Cheers,
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTE
MNG for now - thanks!
On 08/11/2006, at 5:57 AM, Mark Hobson wrote:
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.
I've got a
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.
I've got around to factoring the dependency tree assembling code from
maven-proje
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
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,
Ju
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 obta
