[
https://issues.apache.org/jira/browse/MNG-7498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563418#comment-17563418
]
Michael Bauer commented on MNG-7498:
------------------------------------
The reason I opened this ticket is because the install problem is in Maven
itself. I was using a binary distribution of Maven to build Maven from source.
When I used the binary distribution of Maven to try to install my from-source
build of Maven, it didn't work, for reasons detailed above. Specifically, the
custom clean-the-directory {{clean-target-dir}} POM entry in the Maven source
code finds the .snapshot directory in my target install directory, and refuses
to proceed. I downloaded the Maven source code from the Apache website and
made no changes to it before trying to build it.
I removed the whole {{clean-target-dir}} entry from that POM and now it
installs. (I'm not clear that {{clean-target-dir}} is a good idea, as it seems
unnecessarily destructive, especially if the resulting Maven install is going
into a directory that has other programs already in it.)
My question has nothing to do with a local project. It is me – a sysadmin –
trying to build Maven from source. I have no developers working on Maven who I
can talk to. I was hoping to find one here.
> 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
> Priority: Minor
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> 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.10#820010)
