Plugin isolation and plugin dep downloading

[Jason van Zyl <jv...@maven.org>]

Michal,

What do you think about putting the maven-artifact code into
maven-project (once again) and trying to flush out some of the maven
notions of artifacts and try to use more Wagon notions.

I impetus for this is that now I have complete plugin classloader
isolation but this is really Plexus component isolation and now I would
like to use some Wagon notions in Plexus to generally deal with
downloading dependencies of a component. What I am doing is examining
the plugin JAR and looking at the dependencies, creating a ClassRealm
and populating the ClassRealm with the plugin JAR and all its
dependencies and I want to deal with making sure those dependencies are
available.

We have some notions in maven-artifact for this like the
ArtifactResolver but I was thinking that we might make this something
that could be in Wagon so that the same component could be used in Maven
and Plexus.

Effectively plexus has become a solution for application with a plugin
architecture and I would rather fold notions that we have in
maven-artifact into Wagon itself so that I can use that in Plexus.

Currently I have m2 working with plugin isolation but I have all the
dependencies on my system. I now need a way in Plexus to deal with
downloading the plugin dependencies.

Any thoughts before I wander into the code?

-- 
jvz.

Jason van Zyl
jason@maven.org
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau