What would be involved in displaying a "Project Tree" that is like the
current dependency tree, but instead works off the <parent> hierarchy?

(I don't think it could be done top-down using the <modules> because
those are actually directory names, and don't have to match the child
artifactId.)

Is the data to do this already available in the database?  Can anyone
think of a reason this would be difficult or not advisable?

I opened http://jira.codehaus.org/browse/MRM-1209 and I see Brett put
it in version 1.x, so that's a positive sign. :)

Thanks,
-- 
Wendy

Reply via email to