[MNG-3664] Various unit tests from maven-core fail when run from a directory with space in its path

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-1
• Fix Version/s: 3.0-alpha-1
• Component/s: Integration Tests
• Environment: WinXP & Xubuntu, Sun JDK 1.6.0
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 12/Jul/08 11:01
• Updated: 06/Apr/15 01:53
• Resolved: 23/Nov/08 15:49

Description

OK, not an IT failure but I guess unit test failures count, too

When running the Hudson package from a base directory with a space, say "M:\hud son", the bootstrap job fails with

Tests in error: 
  testBuildFromRepository_StoreProjectByCoordOnlyIfUncached(org.apache.maven.project.workspace.ProjectCachingTest)
  testBuildFromRepository_DontCheckCacheForRELEASEMetaVersion(org.apache.maven.project.workspace.ProjectCachingTest)
  testBuildFromRepository_DontCheckCacheForLATESTMetaVersion(org.apache.maven.project.workspace.ProjectCachingTest)
  testBuildFromFile_StoreByCoordAndFileIfUncached(org.apache.maven.project.workspace.ProjectCachingTest)
  testBuildSectionGroupIdInterpolation(org.apache.maven.project.MavenProjectDynamismTest)
  testRoundTrip(org.apache.maven.project.MavenProjectDynamismTest)
  testShouldPreserveAddedResourceInRestoredState(org.apache.maven.project.MavenProjectDynamismTest)
  testShouldPreserveAddedFilterInRestoredState(org.apache.maven.project.MavenProjectDynamismTest)
  testShouldIncorporateChangedBuildDirectoryViaExpressionsOnNextConcreteCalculation(org.apache.maven.project.MavenProjectDynamismTest)
  testShouldPreserveInitialValuesForPropertiesReferencingBuildPaths(org.apache.maven.project.MavenProjectDynamismTest)
  testShouldAlignCompileSourceRootsInConcreteState(org.apache.maven.project.MavenProjectDynamismTest)

due to test code suffering from Common Bug #6, see attached Surefire report.

Applying the attached patch only makes the show go on until maven-core which then fails with

Tests in error: 
  test_addExtension_usingModel_ShouldLoadExtensionComponent(org.apache.maven.extension.DefaultExtensionManagerTest)
  test_addExtension_usingModel_ShouldLoadCustomLifecycleMappingAndArtifactHandler(org.apache.maven.extension.DefaultExtensionManagerTest)

The console output of these tests is

[WARNING] 
 	DEPRECATION: The POM for the artifact 'org.apache.maven.core.test:test-extension:jar' was invalid or not found on any repositories.
 	This may not be supported by future versions of Maven and should be corrected as soon as possible.
 	Error given: POM 'org.apache.maven.core.test:test-extension' not found in repository: Unable to download the artifact from any repository
 
   org.apache.maven.core.test:test-extension:pom:1
 
 from the specified remote repositories:
   central (file:/M:/hud%20son/runtime/jobs/maven-2.1.x-bootstrap/workspace/trunk/maven-core/target/test-classes/org/apache/maven/extension/test-extension-repo/)
  for project org.apache.maven.core.test:test-extension

and suggests that something (maven-artifact?) is not properly decoding the file URL of central back to "M:\hud son\..."

Issue Links

• is related to: WAGON-112 Clarify value of basedir property for Repository