You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/06/18 09:14:00 UTC

[jira] [Comment Edited] (MNG-7498) Cannot use Maven to install a project on a NetApp volume

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

Michael Osipov edited comment on MNG-7498 at 6/18/22 9:13 AM:
--------------------------------------------------------------

OK, let's try something else. Since I cannot and will not look at something I don't have access to and it is not freely available.
If you want to build your own for reproducibility reasons all you need is the source tarball and invoke {{mvn package}}. In {{apache-maven/target}} is the binary distribution. No installation necessary. This in turn can be used to build Hadoop if you need that, but generally, all binary relases are blessed with my GPG key and are fully reproducible with the same JDK and OS type. I see very little need in your case to build it yourself. What is the justification?


was (Author: michael-o):
OK, let's try something else. Since I cannot and will not look at something I don't have access and it is not freely available.
If you want to build your own for reproducibility reasons all you need is the source tarball and invoke {{mvn package}}. In {{apache-maven/target}} is the binary distribution. No installation necessary. This in turn can be used to build Hadoop if you need that, but generally, all binary relases are blessed with my GPG key and are fully reproducible with the same JDK and OS type. I see very little need in your case to build it yourself. What is the justification?

> 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)