maven/maven-core-it
Jason van Zyl bfb88f0bbd o descriptions of the added integration tests.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162793 13f79535-47bb-0310-9956-ffa450edef68
2004-06-18 02:12:29 +00:00
..
it0000 o updating integration tests, going to hook them up to the ci mechanism. 2004-06-14 22:15:15 +00:00
it0001 o updating integration tests, going to hook them up to the ci mechanism. 2004-06-14 22:15:15 +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
README.txt o descriptions of the added integration tests. 2004-06-18 02:12:29 +00:00
integration-tests.txt o add a prebuild and postbuild hook 2004-06-17 19:36:44 +00:00
maven-core-it.sh build the verifier if it is missing 2004-06-17 20:47:36 +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.