Failed to execute goal … maven-install-plugin … Failed to install artifact … (Access is denied)

15
votes

I often getting the following error when compiling a maven project with NetBeans:

Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-install) on project xxx: Failed to install artifact yyyy: C:\...\.m2\repository\...\yyyy-1.0.0.jar (Access is denied) -> [Help 1]

I don't know what is causing it. Solution is to erase the problematic .m2 content manually and the issue goes. But it is annoying.

Anyone has a permanent solution?

EDIT

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-install) on project Plasma: Failed to install artifact net.dwst:Plasma:jar:1.0.0: C:....m2\repository\net\dwst\Plasma\1.0.0\Plasma-1.0.0.jar (Access is denied) -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-install) on project Plasma: Failed to install artifact net.dwst:Plasma:jar:1.0.0: C:....m2\repository\net\dwst\Plasma\1.0.0\Plasma-1.0.0.jar (Access is denied) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188) at org.apache.maven.cli.MavenCli.main(MavenCli.java:134) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to install artifact net.dwst:Plasma:jar:1.0.0: C:....m2\repository\net\dwst\Plasma\1.0.0\Plasma-1.0.0.jar (Access is denied) at org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:139) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) ... 19 more Caused by: org.apache.maven.artifact.installer.ArtifactInstallationException: Failed to install artifact net.dwst:Plasma:jar:1.0.0: C:....m2\repository\net\dwst\Plasma\1.0.0\Plasma-1.0.0.jar (Access is denied) at org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:110) at org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:103) ... 21 more Caused by: org.sonatype.aether.installation.InstallationException: Failed to install artifact net.dwst:Plasma:jar:1.0.0: C:....m2\repository\net\dwst\Plasma\1.0.0\Plasma-1.0.0.jar (Access is denied) at org.sonatype.aether.impl.internal.DefaultInstaller.install(DefaultInstaller.java:279) at org.sonatype.aether.impl.internal.DefaultInstaller.install(DefaultInstaller.java:190) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.install(DefaultRepositorySystem.java:322) at org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:106) ... 22 more Caused by: java.io.FileNotFoundException: C:....m2\repository\net\dwst\Plasma\1.0.0\Plasma-1.0.0.jar (Access is denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:179) at java.io.FileOutputStream.(FileOutputStream.java:131) at org.sonatype.aether.impl.internal.DefaultFileProcessor.copy(DefaultFileProcessor.java:120) at org.sonatype.aether.impl.internal.DefaultInstaller.install(DefaultInstaller.java:255) ... 25 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

9
javanetbeansmavencompilation
You may post the output of a -e or -X run to give us more details. I suspect some other process is changing file permissions in a subtle way. – Andrew White
What is 'output of a -e or -X' exactly? What should I look for regarding permissions? – Jérôme Verstrynge
Exception stack trace and debugging logs respectively. – Andrew White

9 Answers

11
votes

You may have a typo in your -Dfile argument. Make sure it's pointing to an actual file, not a folder.

I.e. Make sure you don't have -Dfile=C:\lib\jackson when you mean -Dfile=C:\lib\jackson.jar

Targeting a folder can cause this "Access Denied" error, which doesn't seem to make sense for what the actual problem is.

6
votes

This issue started to happen after a NetBeans crash. I finally deleted the content of .m2 and re-installed NetBeans from scratch. The issue disappeared. I am still unclear what would cause it, but it is now gone.

3
votes

Sometimes, when you do mvn clean, you should check if you have opened folders of /target, or other generated resources, so closing all those folders solves the issue.

2
votes

I have experienced this problem in Eclipse Indigo SR2, and I was hoping to try something less drastic than deleting .m2.

I tried to uncheck "Resolve dependencies from Workspace projects" as described in this post, but continued to get the message.

I finally got it working by running mvn clean install from the command line.

0
votes

After about an hour of frustration, here is how I fixed it.

I had upgraded my Eclipse environment and use the maven-install-plugin to add 2 jars that are not in any repository. This had worked previously but now it won't. This plugin automatically adds the jars each time it runs the build. 

<plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-install-plugin</artifactId>
            <version>2.5.2</version>
            <executions>
                <execution>
                    <id>install-external1</id>
                    <phase>clean</phase>
                    <configuration>
                        <file>${basedir}/resources/storm-eventhubs-1.0.2-jar-with-dependencies.jar</file>
                        <repositoryLayout>default</repositoryLayout>
                        <groupId>com.microsoft.eventhubs</groupId>
                        <artifactId>eventhubs-storm-spout</artifactId>
                        <version>1.0.2</version>
                        <packaging>jar</packaging>
                        <generatePom>true</generatePom>
                    </configuration>
                    <goals>
                        <goal>install-file</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>

I went to the .m2 folder and changed the name of the .pom file it was complaining about and bam, it created a new one and ran. Obviously there was a permissions problem in the folder structure. Give it a try!

0
votes

I got this error too, it was solved by creating a simple maven project.

Steps:-

  1. Create a simple maven project along with your existing project.
  2. Build this new project.
  3. If it builds successfully, build your existing maven project.
0
votes

for some reasons(windows 7) i don’t have permission to access the specified folder,so either you run the Maven or your IDE as administrator or so try to access the folder and you will have warning popup and you have to click Continue to permanently get access to this folder, so your user account is added to the ACL for the folder , and that's it !

0
votes

I got this error too. I resolved this by unchecking the folder attributes read-only and Hidden.

0
votes

i faced the same issue ,(for linux based users) the reason for me was the folder it was trying to access had root privilege , so any normal user could not access it.

to resolve this there are 2 steps :
1. add a sudo to the command

sudo mvn clean compile    # or any other mvn command

2. delete the parent folder for the project (not the .m2, folder with name same as the project) and then retry your command

sudo rm -r your-folder/    #  inside ./m2 folder

mnv clean compile  # inside your project