maven/maven-core-it
John Dennis Casey a949eb66de o Removed GoalDecorationPhase, since goal decoration is now a part of the model
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
2004-08-26 04:40:02 +00:00
..
it0000 o Adding <modelVersion>. 2004-07-01 02:11:35 +00:00
it0001 o Adding <modelVersion>. 2004-07-01 02:11:35 +00:00
it0002 Use maven.properties in all code instead of build.properties. 2004-07-27 13:23:36 +00:00
it0003 Use maven.properties in all code instead of build.properties. 2004-07-27 13:23:36 +00:00
it0004 Use maven.properties in all code instead of build.properties. 2004-07-27 13:23:36 +00:00
it0005 o the pom should definitely be installed but how snapshots are handled 2004-08-15 16:18:21 +00:00
it0006 o Removed GoalDecorationPhase, since goal decoration is now a part of the model 2004-08-26 04:40:02 +00:00
it0007 fixing name of expected result 2004-08-10 17:54:40 +00:00
it1000 o Adding <modelVersion>. 2004-07-01 02:11:35 +00:00
it1001 o Adding <modelVersion>. 2004-07-01 02:11:35 +00:00
it1002 o Adding <modelVersion>. 2004-07-01 02:11:35 +00:00
it1003 o Adding <modelVersion>. 2004-07-01 02:11:35 +00:00
.cvsignore ignore logs 2004-08-17 20:50:42 +00:00
README.txt o Added comment to integration tests README describing it0006 (goal decoration integration test) 2004-08-10 18:03:39 +00:00
integration-tests.txt adding it0007 2004-08-10 17:56:23 +00:00
maven-core-it.sh o toss out the log of the build if something goes wrong, otherwise just 2004-08-15 16:52:07 +00:00

README.txt

-------------------------------------------------------------------------------
it0000: The simplest of builds. We have one application class and one test
        class. There are no resources, no source generation, no resource
        generation and a the super model is employed to provide the build
        information.

it0001: Builds upon it0000: we add an application resource that is packaged
        up in the resultant JAR.

it0002: Builds upon it0001: we add the download of a dependency. We delete
        the JAR from the local repository and make sure it is there post build.
       
it0003: Builds upon it0001: we add a jar installation step. We delete the JAR
        from the local repository to make sure it is there post build.
       
it0004: The simplest of pom installation. We have a pom and we install it in
        local repository.
       
it0005: The simplest of pom installation. We have a snapshot pom and we install
        it in local repository.

it0006: Simple goal decoration. We introduce a preGoal and a postGoal to the
		'compiler:compile' goal.

it0007: We specify a parent in the POM and make sure that it is downloaded as
        part of the process.        

-------------------------------------------------------------------------------

- generated sources
- generated resources from sources
- generated resources from generated sources
- filtered resources
- build that requires a plugin download
- transitive dependencies
- goal attainment not requiring depedency resolution
- goal attainment where a POM is not required: this is a case where
  we are using mgen to create new applications and project structures
  which is used by the m2 geronimo plugin and tools like the "setup"
  goal which brings a project to life from scratch using something like:
  m2 --setup xstream --version 1.0

- write a small program to generate a massively nested build
  which which use the reactor and inheritence. we need to have
  integration tests that go far beyond what the average user
  would ever setup.
  
- project with a cyclic dependency

-------------------------------------------------------------------------------
These are a set of builds that contain known errors. The errors should be
captured and reported in a useful manner to the user. We will start at it1000
for intentially flawed builds.
-------------------------------------------------------------------------------
it1000: A build which contains a malformed pom.xml. We have intentionally 
        created a mismatch in the first element. We have:
        <projectX>...</project>
-------------------------------------------------------------------------------
it1001: A build whose pom.xml does not contain a <groupId/> element.
-------------------------------------------------------------------------------
it1002: A build with a syntax error in the first field declaration.
-------------------------------------------------------------------------------
it1003: A build with a simple test failure.
-------------------------------------------------------------------------------

- checksum mismatch