[ 
https://issues.apache.org/jira/browse/MNG-7498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555765#comment-17555765
 ] 

Michael Bauer commented on MNG-7498:
------------------------------------

To provide more detail, I was building the latest Maven so I could install 
Hadoop.  I downloaded the source tarball from the URL provided on 
[https://maven.apache.org/download.cgi.]  The tarball unpacked with the 
following code in apache-maven/pom.xml:

 

          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-clean-plugin</artifactId>
            <executions>
              <execution>
                <goals>
                  <goal>clean</goal>
                </goals>
                <id>clean-target-dir</id>
                <phase>prepare-package</phase>
                <configuration>
                  <excludeDefaultDirectories>true</excludeDefaultDirectories>
                  <filesets>
                    <fileset>
                      <directory>${distributionTargetDir}</directory>
                    </fileset>
                  </filesets>
                </configuration>
              </execution>
            </executions>
          </plugin>

 

This appears to have been the cause of the problem.  I removed that entire 
block from apache-maven/pom.xml.  The project built and installed.

 

I don't know if this is properly a bug – it sure looks like one – because it is 
specific to people using NetApp's snapshot feature.  The configuration file 
came from the Maven source code tarball as downloaded.

> Cannot use Maven to install a project on a NetApp volume
> --------------------------------------------------------
>
>                 Key: MNG-7498
>                 URL: https://issues.apache.org/jira/browse/MNG-7498
>             Project: Maven
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: 3.8.6
>         Environment: RHEL 7 with a NetApp file server.
>            Reporter: Michael Bauer
>            Assignee: Michael Osipov
>            Priority: Minor
>             Fix For: waiting-for-feedback
>
>
> By default, every directory in a volume that is exported from a Network 
> Appliance contains a directory named '.snapshot'.  That directory is created 
> and maintained by the NetApp.  It is read-only; it cannot be deleted or 
> altered.
>  
> Maven appears to refuse to install into a directory that is not cleaned out, 
> and because of the nature of the subdirectory .snapshot it cannot delete that 
> subdirectory.  Ergo, I get errors like:
>  
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-clean-plugin:3.1.0:clean (clean-target-dir) on 
> project apache-maven: Failed to clean project: Failed to delete 
> /usr/sup/apache-maven-3.8.6/.snapshot -> [Help 1]
>  
> /usr/sup is on a NetApp volume.  I did not ask for 'clean' on this install:
>  
> % mvn -DdistributionTargetDir='/usr/sup/apache-maven-3.8.6' install
>  
> I am a sysadmin, not a developer.  My ideal is repeatable builds, so I would 
> prefer to have a way to do this that uses released software.  End goal: a 
> professor wants Hadoop, and Hadoop wants to be installed with a newer version 
> of Maven than RHEL 7 provides.  If I can't install Maven with Maven, I don't 
> expect that installing Hadoop with Maven will work either.
>  
> Is there a way to tell Maven to ignore the .snapshot subdirectory in an 
> otherwise empty target directory?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to