o Removed PluginDownloadPhase, since plugin resolution/download has to be a part of the prereq and pre/postGoal resolution, too
o Changed DefaultMaven to execute the session lifecycle, and the component wiring to likewise wire the DefaultMaven with a session lifecycle manager
o Removed the org.apache.maven.decoration package and its contents, since this is all in the model now
o Fixed the GoalResolutionPhase to verify each goal's plugin in turn as it resolves prereqs, preGoals and postGoals
o Fixed the GoalResolutionPhaseTest to work with the new resolution model
o Added a new createGoalExecutionContext to the MavenTestCase base class, to allow me to inject a MavenProject directly rather than a pom file
o Fixed the MavenLifecycleManagerTest to only expect 4 lifecycle phases, now than the plugin resolution and goal decoration phases are obsoleted
o All builds on local machine, but will depend on plexus-0.17.jar/pom and plexus-artifact-container-1.0-alpha-1.jar/pom to build on beaver
o I uploaded plexus-artifact-container-1.0-alpha-1.jar to ${plexus.home}/dist, but cannot upload POMs due to priveleges problem in poms dir.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163007 13f79535-47bb-0310-9956-ffa450edef68
o Changed the embedder/container used to be the new artifact-aware container (plexus-artifact-container-1.0-alpha-1)
o Added new dependency to maven-core for artifact-container.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163006 13f79535-47bb-0310-9956-ffa450edef68
o Added testing to show failure to merge resources from parent into child build which specifies a build without these elements
o Fixed resource blending for child build sections which don't specify them.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163001 13f79535-47bb-0310-9956-ffa450edef68
this is not the way i want the installing mechanism to work (i.e. copying
the same class around ...) but folks want to install plugins so i'll just
pop this in for now.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162997 13f79535-47bb-0310-9956-ffa450edef68
NOTE: this is not how I would like this handled, the artifact layer will
be responsible for dealing with metadata in a way that is controlled by
the artifact handler.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162982 13f79535-47bb-0310-9956-ffa450edef68
vs releases needs to be clarified as the use of snapshots I'm trying to
encapsulate into a single class which i haven't fully resolved. doing
if ( SNAPSHOT )
{ ... }
is not what we want ...
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162981 13f79535-47bb-0310-9956-ffa450edef68
-> bascially the mechanism is the same as the one we use for the goal
execution lifecycle
This first cut is so John can see as we're discussing the session stuff
at the moment and I need to get this working in order to push all notions
of artifact handling out of MavenProject.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162969 13f79535-47bb-0310-9956-ffa450edef68
it really is. Making way for the notion of a MavenSessionExecutionContext
and it is looking like we will end up with two lifecycles. Where we are
dealing with notions of goals and sessions: some operations need to be
done at the session level and don't need to be repeated for the execution
of every goal.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162968 13f79535-47bb-0310-9956-ffa450edef68
Trygve Laugstol
Emmanuel Venisse
John Dennis Casey
Jason van Zyl
Brett Leslie Porter