Hi,
This is a bit brute force, but I hope it'll be helpful.
I've written something that utilises dependency-tree to generate a set
of files representing the determined artifact tree for every POM in a
repository from a CLI [1], and a test [2] that will then re-evaluate
them with a different version of maven-artifact and compare them to
the 2.0.8 reference rendering. So far I've found that 2.1 removed the
transitive flattening functionality [3] - I haven't run further yet
though.
I would think this could be extended to also evaluate the rendered
project model so we could refactor that with a bit more confidence too.
I've been testing against a cut down, older version of central I have
here (about ~12000 projects). I would think the best result would be
to run it against a copy of central, and also a repository of POMs
from projects that aren't deployed into that repository but exhibit
complex dependency behaviour. However, this is at least a start.
Would others find this helpful?
Of course scanning this continues to highlight the amount of metadata
that we have that is plain invalid (it doesn't even parse, let alone
the things that are not "correct"). Part of my motivation here is that
I want to start getting to work on long standing proposals and
thoughts that would land in maven-artifact, and I believe some of
those can facilitate a more managed cleanup of central without
impacting existing builds.
Cheers,
Brett
[1]
http://svn.apache.org/viewvc/archiva/trunk/archiva-modules/archiva-base/archiva-consumers/archiva-dependency-tree-consumer/
[2]
http://svn.apache.org/viewvc/maven/sandbox/trunk/maven/maven-artifact-tree-tester/
[3] http://jira.codehaus.org/browse/MARTIFACT-12
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
