maven/maven-core-it
Jason van Zyl f9e2d61a7f o take the groupId out for the test
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162812 13f79535-47bb-0310-9956-ffa450edef68
2004-06-19 19:58:49 +00:00
..
it0000 o adding goals.txt to integration tests. 2004-06-18 02:13:16 +00:00
it0001 o adding goals.txt to integration tests. 2004-06-18 02:13:16 +00:00
it0002 This commit was generated by cvs2svn to compensate for changes in r300, 2004-06-18 02:08:23 +00:00
it0003 Initial revision 2004-06-18 02:08:22 +00:00
it1000 Initial revision 2004-06-18 11:56:03 +00:00
it1001 o take the groupId out for the test 2004-06-19 19:58:49 +00:00
it1002 o fixing POMs 2004-06-19 00:46:29 +00:00
it1003 Initial revision 2004-06-18 11:56:03 +00:00
README.txt *** empty log message *** 2004-06-18 11:59:01 +00:00
integration-tests.txt o adding goals.txt to integration tests. 2004-06-18 02:13:16 +00:00
maven-core-it.sh o use relative paths all the way and cygwin is happy as well as unix 2004-06-19 18:13:25 +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.

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

- 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.
  
-------------------------------------------------------------------------------
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