maven/maven-core-it
John Dennis Casey 459737fa5f Resolving MNG-851. Using MavenProject.getFile() rather than constructing new. Also fixed maven-deploy-plugin with similar bug.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@280405 13f79535-47bb-0310-9956-ffa450edef68
2005-09-12 20:08:01 +00:00
..
it0000 check we get a report out of surefire 2005-08-12 02:45:57 +00:00
it0001 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it0002 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it0003 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it0004 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it0005 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it0006 use built verifier plugin in itest 2005-05-21 15:46:15 +00:00
it0007 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it0008 these use the it plugin, also need plugin repository setting 2005-07-26 15:42:33 +00:00
it0009 these use the it plugin, also need plugin repository setting 2005-07-26 15:42:33 +00:00
it0010 Update all versions to beta-1-SNAPSHOT 2005-06-27 15:29:14 +00:00
it0011 Update all versions to beta-1-SNAPSHOT 2005-06-27 15:29:14 +00:00
it0012 o adding pluginRepositories element to match the other ITs which use the 2005-09-10 12:03:21 +00:00
it0013 o Fixing DoxiaMojo (there was an API incompatibility there, having to do with FileUtils...not sure if there is something that didn't get deployed, or what) 2005-07-29 23:26:42 +00:00
it0014 add test compilation to integration test 2005-05-08 21:39:30 +00:00
it0015 o Fixing DoxiaMojo (there was an API incompatibility there, having to do with FileUtils...not sure if there is something that didn't get deployed, or what) 2005-07-29 23:26:42 +00:00
it0016 PR: MNG-415 2005-06-16 15:02:07 +00:00
it0017 reformat 2005-07-22 13:52:21 +00:00
it0018 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it0019 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it0020 o Fixing DoxiaMojo (there was an API incompatibility there, having to do with FileUtils...not sure if there is something that didn't get deployed, or what) 2005-07-29 23:26:42 +00:00
it0021 Fixing problem with using distributionManagement repository definition for download of plugins.xml metadata. 2005-07-12 20:08:21 +00:00
it0022 add correct plugin repository 2005-07-28 00:51:36 +00:00
it0023 add correct plugin repository 2005-07-28 00:51:36 +00:00
it0024 fix incorrect test (execution cannot affect something already bound by packaging) 2005-06-18 16:01:48 +00:00
it0025 add correct plugin repository 2005-07-28 00:51:36 +00:00
it0026 add correct plugin repository 2005-07-28 00:51:36 +00:00
it0027 add correct plugin repository 2005-07-28 00:51:36 +00:00
it0028 Resolving: MNG-496 2005-06-20 20:11:01 +00:00
it0029 Fix it number in artifact name 2005-06-27 13:14:49 +00:00
it0030 reenable tests 2005-07-22 15:37:46 +00:00
it0031 Fixing issues related to MNG-377, where the plugins.xml metadata was being mishandled. Separated updating of this metadata into a separate mojo, bound to the 'package' phase, and put in a validator for the POM (POM has to have distributionRepository now for maven-plugin's) which is bound to the 'validate' phase. Put together an integration test that uses modello:java as a case where the pluginGroups must be consulted. Also had to change the Verifier to check a verifier.properties for failOnErrorOutput, which will suppress IT failures based on [ERROR] log output (modello outputs one of these, and kills the IT unnecessarily). 2005-07-11 22:08:58 +00:00
it0032 integration tests for the required maven version test 2005-07-18 11:59:46 +00:00
it0033 fix the integration test after the default location changed 2005-08-15 11:47:18 +00:00
it0034 PR: MNG-613 2005-09-09 06:49:59 +00:00
it0035 PR: MNG-507 2005-07-22 00:31:44 +00:00
it0036 Working on: MNG-607 2005-07-26 03:55:37 +00:00
it0037 Working on: MNG-607 2005-07-26 03:55:37 +00:00
it0038 Working on: MNG-607 2005-07-26 03:55:37 +00:00
it0039 Working on: MNG-607 2005-07-26 03:55:37 +00:00
it0040 snapshots have moved 2005-07-26 14:24:38 +00:00
it0041 extra check on download 2005-07-28 06:30:55 +00:00
it0042 Adding system scope...uses scope == 'system' and systemPath in dependency. SystemPath was chosen over mappings inside the setings.xml for scalability, heritability, and injectability (via managed deps). 2005-08-31 07:39:01 +00:00
it0043 cleanup it0043 2005-08-01 01:05:38 +00:00
it0044 Resolving: MNG-282 2005-08-03 20:43:58 +00:00
it0045 Resolving: MNG-95 2005-08-04 21:14:51 +00:00
it0046 Resolving: MNG-95 2005-08-04 21:14:51 +00:00
it0047 add a test case to illustrate why we have to make compile time dependencies transitive as compile, not runtime as we'd like. 2005-08-09 23:31:14 +00:00
it0048 Fixing problem with mojo configuration merges between parameter configuration keyed by alias and by name within the POM, along with configuration within the MojoDescriptor. 2005-08-12 02:25:26 +00:00
it0049 add pre build hook to remove the core it plugin so it is always updated 2005-08-11 05:14:58 +00:00
it0050 it0050: fixed expected results and adding it to integration-tests (again). 2005-08-17 21:33:02 +00:00
it0051 Fixing some things: 2005-08-17 19:23:45 +00:00
it0052 Adding inverse test of it0051. 2005-08-17 19:36:05 +00:00
it0053 Attempting again to fix the expectations... 2005-08-23 03:30:23 +00:00
it0054 Adding integration itest it0054 to verify that MNG-479 is fixed. 2005-08-22 21:02:07 +00:00
it0055 Resolving: MNG-643 2005-08-22 23:14:34 +00:00
it0056 Resolving: MNG-643 2005-08-22 23:14:34 +00:00
it0057 Resolving: MNG-766. 2005-08-23 22:11:07 +00:00
it0058 Resolving: MNG-773 2005-08-24 20:31:29 +00:00
it0059 Resolving: MNG-666 2005-08-25 03:08:10 +00:00
it0060 Resolving: MNG-732 2005-08-25 20:19:40 +00:00
it0061 Resolving (Cannot Reproduce): MNG-731 2005-08-25 22:53:43 +00:00
it0062 clean up repository item too 2005-09-12 13:45:31 +00:00
it0063 Adding system scope...uses scope == 'system' and systemPath in dependency. SystemPath was chosen over mappings inside the setings.xml for scalability, heritability, and injectability (via managed deps). 2005-08-31 07:39:01 +00:00
it0064 test setter is used instead of field population 2005-09-11 05:05:28 +00:00
it0065 add integration test for parent.getBasedir() 2005-09-12 09:27:57 +00:00
it0066 Resolving MNG-851. Using MavenProject.getFile() rather than constructing new. Also fixed maven-deploy-plugin with similar bug. 2005-09-12 20:08:01 +00:00
it1000 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it1001 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it1002 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it1003 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it1004 remove old cvs ignore files 2005-06-07 05:24:51 +00:00
it1005 IT for testing failure when duplicate goal names are specified in multiple mojos... 2005-05-06 00:36:00 +00:00
it1006 Resolving issue: MNG-493 2005-06-21 03:57:17 +00:00
it1007 integration tests for the required maven version test 2005-07-18 11:59:46 +00:00
it1008 PR: MNG-505 2005-07-20 06:53:47 +00:00
it1009 PR: MNG-598 2005-07-26 09:04:32 +00:00
it1010 PR: MNG-598 2005-07-26 09:04:32 +00:00
it1011 Resolving: MNG-95 2005-08-04 21:14:51 +00:00
it1012 Resolving: MNG-652 2005-08-12 03:02:35 +00:00
it1013 o Improving toString for Dependency in the 4.0.0 version codeSegment in maven.mdo 2005-08-12 21:55:00 +00:00
it2000 Resolving: MNG-592 (again) 2005-08-09 16:11:40 +00:00
README.txt Resolving MNG-851. Using MavenProject.getFile() rather than constructing new. Also fixed maven-deploy-plugin with similar bug. 2005-09-12 20:08:01 +00:00
integration-tests.txt Resolving MNG-851. Using MavenProject.getFile() rather than constructing new. Also fixed maven-deploy-plugin with similar bug. 2005-09-12 20:08:01 +00:00
maven-core-it.bat o Changed the it scripts to remove the $MAVEN_OPTS from the verifier launch line, so that we can remotely debug an integration test execution (rather than getting stuck on the verifier execution itself) 2005-07-29 03:07:56 +00:00
maven-core-it.sh still allow debugging the verifier, and don't discard all MAVEN_OPTS (I need it to have my home directory set correctly!) 2005-07-30 02:13:16 +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: Integration test for the verifier plugin.

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 plugin binds to a phase and the plugin must
        be downloaded from a remote repository before it can be executed. This
        test also checks to make sure that mojo parameters are aligned to the 
        project basedir when their type is "java.io.File".
        
it0009: Test plugin configuration and goal configuration that overrides what the
        mojo has specified.
        
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.
        # TODO: must correct the assumptions 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 POM configuration by settings the -source and -target for the
        compiler to 1.4

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.

it0016: Test a WAR generation

it0017: Test an EJB generation

it0018: Ensure that managed dependencies for dependency POMs are calculated
        correctly when resolved. Removes commons-logging-1.0.3 and checks it is
        redownloaded.

it0019: Test that a version is managed by pluginManagement in the super POM

it0020: Test beanshell mojo support.

it0021: Test pom-level profile inclusion (this one is activated by system
        property).

it0022: Test profile inclusion from profiles.xml (this one is activated by system
        property).

it0023: Test profile inclusion from settings.xml (this one is activated by an id
        in the activeProfiles section).

it0024: Test usage of <executions/> inside a plugin rather than <goals/>
        that are directly inside th plugin.

it0025: Test multiple goal executions with different execution-level configs.

it0026: Test merging of global- and user-level settings.xml files.

it0027: Test @execute with a custom lifecycle, including configuration

it0028: Test that unused configuration parameters from the POM don't cause the
        mojo to fail...they will show up as warnings in the -X output instead.

it0029: Test for pluginManagement injection of plugin configuration.

it0030: Test for injection of dependencyManagement through parents of 
        dependency poms.

it0031: Test usage of plugins.xml mapping file on the repository to resolve
        plugin artifactId from it's prefix using the pluginGroups in
        the provided settings.xml.

it0032: Tests that a specified Maven version requirement that is lower doesn't cause any problems

it0033: Test an EAR generation

it0034: Test version range junit [3.7,) resolves to 3.8.1

it0035: Test artifact relocation.

it0036: Test building from release-pom.xml when it's available

it0037: Test building with alternate pom file using '-f'

it0038: Test building project from outside the project directory using '-f'
        option

it0039: Test reactor for projects that have release-pom.xml in addition to
        pom.xml. The release-pom.xml file should be chosen above pom.xml for
        these projects in the build.

it0040: Test the use of a packaging from a plugin

it0041: Test the use of a new type from a plugin

it0042: Test that the reactor can establish the artifact location of known projects for dependencies

it0043: Test for repository inheritence - ensure using the same id overrides the defaults

it0044: Test --settings CLI option

it0045: Test non-reactor behavior when plugin declares "@requiresProject false"

it0046: Test fail-never reactor behavior. Forces an exception to be thrown in
        the first module, but checks that the second modules is built.

it0047: Test the use case for having a compile time dependency be transitive: 
        when you extend a class you need its dependencies at compile time.

it0048: Verify that default values for mojo parameters are working (indirectly, 
        by verifying that the Surefire mojo is functioning correctly).

it0049: Test parameter alias usage.

it0050: Test surefire inclusion/exclusions

it0051: Test source attachment when -DperformRelease=true is specified.

it0052: Test that source attachment doesn't take place when
        -DperformRelease=true is missing.

it0053: Test that attached artifacts have the same buildnumber and timestamp
        as the main artifact. This will not correctly verify until we have
        some way to pattern-match the buildnumber/timestamp...

it0054: Test that locally defined repositories override those from the super
        POM. This is from MNG-479.

it0055: Test that source includes/excludes with in the compiler plugin config.
        This will test excludes and testExcludes...

it0056: Test that multiple executions of the compile goal with different
        includes/excludes will succeed.

it0057: Verify that scope == 'provided' dependencies are available to tests.

it0058: Verify that profiles from settings.xml do not pollute module lists
        across projects in a reactorized build.

it0059: Verify that maven-1 POMs will be ignored but not stop the resolution
        process.

it0060: Test aggregation of list configuration items when using
        'combine.children=append' attribute. Specifically, merge the list of
        excludes for the testCompile mojo.

it0061: Verify that deployment of artifacts to a legacy-layout repository
        results in a groupId directory of 'the.full.group.id' instead of
        'the/full/group/id'.

it0062: Test that a deployment of a snapshot falls back to a non-snapshot repository if no snapshot repository is
        specified.

it0063: Test the use of a system scoped dependency to tools.jar.

it0064: Test the use of a mojo that uses setters instead of private fields
        for the population of configuration values.

it0065: Test that the basedir of the parent is set correctly.

it0066: Test that nonstandard POM files will be installed correctly.

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

- 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
-------------------------------------------------------------------------------
it1005: A build with two mojo java sources that declare the same goal.
-------------------------------------------------------------------------------
it1006: Tests collision on default execution id. Should throw an 
        IllegalStateException, since the model is incorrect.
-------------------------------------------------------------------------------
it1007: Should fail due to requiring a future version of Maven.
-------------------------------------------------------------------------------
it1008: Should fail due to requiring a version range for junit that doesn't exist
        in the repository. Currently succeeds (MNG-614)
-------------------------------------------------------------------------------
it1009: Tests packaging from a plugin fails when extensions is not true.
-------------------------------------------------------------------------------
it1010: Tests a type from a plugin fails when extensions is not true.
-------------------------------------------------------------------------------
it1011: Tests the fail-at-end reactor behavior. First module fails, and second
        should also run but not fail. End result should be failure of the build.
-------------------------------------------------------------------------------
it1012: Test that the DefaultLifecycleExecutor will throw an exception when
        encountering an unknown packaging.
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
These are a set of builds that are more complex than single-project or reactor
invocations. They follow a process external to maven itself, invoking
different lifecycle phases and/or goals on multiple projects within each test
directory in order to accomplish their aims. 

NOTE: Currently, there is no verification process...
-------------------------------------------------------------------------------
it2000: Test resolution of plugin by prefix from the first plugin repository
        in a list. This is accomplished by creating a local "remote" repo, and
        deploying a plugin there. Then, in another project, that plugin's goal
        is invoked directly with the plugin's groupId being included in the
        pluginGroups for the build. This second build should pickup the
        plugins.xml for the aforementioned plugin from the first repository
        and execute. This should resolve MNG-592.
-------------------------------------------------------------------------------