org.apache.maven.project.inheritance.t09

Class ProjectInheritanceTest

java.lang.Object

junit.framework.Assert

junit.framework.TestCase

org.codehaus.plexus.PlexusTestCase

org.apache.maven.project.AbstractMavenProjectTestCase

org.apache.maven.project.inheritance.AbstractProjectInheritanceTestCase

org.apache.maven.project.inheritance.t09.ProjectInheritanceTest

All Implemented Interfaces:

junit.framework.Test

public class ProjectInheritanceTest
extends AbstractProjectInheritanceTestCase

Verifies exclusions listed in dependencyManagement are valid for transitive dependencies.

Author:

Patrick Schneider

Field Summary

Fields inherited from class org.apache.maven.project.AbstractMavenProjectTestCase

projectBuilder, repositorySystem

Constructor Summary

Constructors

Constructor and Description
ProjectInheritanceTest()

Method Summary

Modifier and Type	Method and Description
void	testDependencyManagementExclusionDoesNotOverrideGloballyForTransitives() Setup exactly the same as the above test, except that the child project now depends upon d, which has a transitive dependency on c.
void	testDependencyManagementExclusionsExcludeTransitively() How the test project is set up: 1.

Methods inherited from class org.apache.maven.project.inheritance.AbstractProjectInheritanceTestCase

getLocalRepositoryPath, getTestSeries, projectFile, projectFile

Methods inherited from class org.apache.maven.project.AbstractMavenProjectTestCase

customizeContainerConfiguration, getCustomConfigurationName, getFileForClasspathResource, getLocalRepository, getProject, getProjectBuilder, getProjectWithDependencies, initRepoSession, setUp, tearDown

Methods inherited from class org.codehaus.plexus.PlexusTestCase

customizeContext, getBasedir, getClassLoader, getConfigurationName, getContainer, getResourceAsStream, getTestConfiguration, getTestConfiguration, getTestFile, getTestFile, getTestPath, getTestPath, lookup, lookup, lookup, lookup, release, setupContainer, teardownContainer

Methods inherited from class junit.framework.TestCase

assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, countTestCases, createResult, fail, fail, failNotEquals, failNotSame, failSame, format, getName, run, run, runBare, runTest, setName, toString

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Constructor Detail

ProjectInheritanceTest

public ProjectInheritanceTest()

Method Detail

testDependencyManagementExclusionsExcludeTransitively

public void testDependencyManagementExclusionsExcludeTransitively()
                                                           throws Exception

How the test project is set up: 1. dependencyManagement lists dependencies on a & b, with an exclusion on c in b. 2. the child project lists a dependency on project a only 3. a depends on b (which is transitive to the child project), and b depends on c. We should see that the resulting size of collected artifacts is two: a & b only.

Throws:

Exception

testDependencyManagementExclusionDoesNotOverrideGloballyForTransitives

public void testDependencyManagementExclusionDoesNotOverrideGloballyForTransitives()
                                                                            throws Exception

Setup exactly the same as the above test, except that the child project now depends upon d, which has a transitive dependency on c. Even though we did list an exclusion on c, it was only from within the context of project b. We will pick up project c in this case because no restrictions were placed on d. This demonstrates that a, b, c, & d will all be collected.

Throws:

Exception