maven/maven-core-it
Brett Leslie Porter b70904c7a3 make sure it0013 fails even under a non-clean repo
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163431 13f79535-47bb-0310-9956-ffa450edef68
2005-02-28 22:47:19 +00:00
..
it0000 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0001 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0002 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0003 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0004 Add log.txt 2004-12-06 10:51:58 +00:00
it0005 Add log.txt 2004-12-06 10:51:58 +00:00
it0006 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0007 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0008 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0009 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0010 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0011 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it0012 amend interpolation IT 2005-02-23 03:56:44 +00:00
it0013 make sure it0013 fails even under a non-clean repo 2005-02-28 22:47:19 +00:00
it0014 Initial revision 2005-02-24 04:52:04 +00:00
it0015 o Completed marmalade-mojo support, tested with m2 bootstrap with empty local repo and maven-core pegged at 2/26/2005. 2005-02-28 18:29:47 +00:00
it1000 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it1001 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it1002 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
it1003 o updating tests to reflect the addition of the lifecyle 2005-02-16 07:11:14 +00:00
README.txt add description of it0014 2005-02-27 05:37:31 +00:00
integration-tests.txt o Completed marmalade-mojo support, tested with m2 bootstrap with empty local repo and maven-core pegged at 2/26/2005. 2005-02-28 18:29:47 +00:00
maven-core-it.bat MNG-86. Fix bootstrap failures when M2_HOME contains spaces. 2004-09-30 08:49:20 +00:00
maven-core-it.sh temporary fix for cygwin - need CommandLine to somehow call the cygwin m2 2004-12-15 11:27:43 +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.        

it0008: Simple goal decoration where a preGoal belongs to a plugin that must
        be downloaded from a remote repository before it can be executed.
        
it0009: Simple goal decoration where a postGoal belongs to a plugin that must
        be downloaded from a remote repository before it can be executed.        
        
it0010: Since the artifact resolution does not use the project builder, we must
        ensure that the full hierarchy of all dependencies is resolved. This
        includes the dependencies of the parent-pom's of dependencies. This test
        will check this, by depending on classworlds, which is a dependency of
        maven-component, which is the parent of maven-plugin, which is an
        explicit dependency of this test.
        
it0011: Test specification of dependency versions via <dependencyManagement/>.

it0012: Test simple POM interpolation

it0013: Test plugin-plugin, which tests maven-plugin-tools-api and 
        maven-plugin-tools-java. This will generate a plugin descriptor from 
        java-based mojo sources, install the plugin, and then use it.

it0014: Test a JAR override by file.

it0015: Test marmalade-driven mojo support. This will compile supporting java
        classes (mmld tag & taglib), generate plugin descriptor from mmld script,
        install the plugin, and finally use the new plugin.
-------------------------------------------------------------------------------

- 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