2004-05-21 13:25:02 -04:00
|
|
|
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.
|
|
|
|
|
2004-06-17 22:12:29 -04:00
|
|
|
it0001: Builds upon it0000: we add an application resource that is packaged
|
2004-05-21 13:25:02 -04:00
|
|
|
up in the resultant JAR.
|
|
|
|
|
2004-06-17 22:12:29 -04:00
|
|
|
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.
|
|
|
|
|
2004-05-21 13:25:02 -04:00
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
- generated sources
|
|
|
|
- generated resources from sources
|
|
|
|
- generated resources from generated sources
|
|
|
|
- filtered resources
|
|
|
|
- build that requires a plugin download
|
|
|
|
- transitive dependencies
|
2004-05-25 08:49:13 -04:00
|
|
|
- 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
|
2004-05-21 13:25:02 -04:00
|
|
|
|
|
|
|
- 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.
|