Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: 2.2.1, 3.0-beta-1
-
Fix Version/s: None
-
Component/s: Bootstrap & Build
-
Labels:None
-
Environment:OpenSolaris build 135, build 138. Java 1.6. Generic hardware
-
Complexity:Intermediate
-
Patch Submitted:Yes
-
Number of attachments :
Description
When running ant in the top level of the source distribution, the extract-assembly target uses the ant <delete/> task
to ensure that a directory is created.
This is undocumented in the installation guide and README.txt file, and unnecessary - ant's <Mkdir/> task runs the
equivalent of "mkdir -p" which ensures that the directory is created anyway.
patch against maven-3 trunk (though the issue exists in maven-2.2.1 release also)
blinder:maven-3 $ svn diff build.xml
Index: build.xml
===================================================================
— build.xml (revision 941139)
+++ build.xml (working copy)
@@ -237,7 +237,6 @@
<target name="extract-assembly" depends="init,maven-assembly" description="extracts the maven assembly into maven.home">
<echo>Extracting assembly to $
<!-- If we are starting from scratch make sure the directory is created -->
- <delete dir="${maven.home.effective}" />
<mkdir dir="${maven.home.effective}" />
<unzip src="${maven.assembly}" dest="${maven.home.dirname}
" />
<chmod perm="+x">
Issue Links
- is related to
-
MNG-4352
Misleading error when bootstrapping Maven build with unexpected installation directory
-
The cleaning of maven.home is a desired step before extracting the generated assembly.
Regarding validation of the specified home directory, the script for 2.2.x has already been improved as per
MNG-4352, the build script for 3.x now prompts the user if the specified directory already exists.