You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Candice Tosi Michelon (Jira)" <ji...@apache.org> on 2023/10/25 13:07:00 UTC
[jira] [Updated] (MINSTALL-194) Fail to install snapshot artifact when clean phase is used
[ https://issues.apache.org/jira/browse/MINSTALL-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Candice Tosi Michelon updated MINSTALL-194:
-------------------------------------------
Description:
{*}After ugrading maven from version 3.6.3 to 3.9.4 a few maven projects started failing in the install phase with the error below{*}:
Failed to install artifact xxxxxx:jar:1.1-SNAPSHOT: xxxxx-1.1-SNAPSHOT.jar.3154215231322123456.tmp -> xxxxx-1.1-SNAPSHOT.jar -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install) on project xxxxx: Failed to install artifact xxxxx:jar:1.1-SNAPSHOT: xxxxx-1.1-SNAPSHOT.jar
Caused by: org.apache.maven.plugin.MojoExecutionException:
Caused by: org.eclipse.aether.installation.InstallationException:
Caused by: java.nio.file.AccessDeniedException:
*Command used:* mvn clean install
*All the projects affected have the following characteristics:*
* Multi-modules
* The clean phase is used at least once
* The pmd check is performed
* A jar snapshot of the module already existis in the maven repository folder (.m2)
This is not a blocker issue because *it is still possible to build the projects and install the snapshots* in the local repository if the follwoing options are used:
* Option 1: Avoid using the clean phase. Use only 'mvn install'.
* Option 2: Use the following mvn commands:
** mvn clean
** mvn install -N
** mvn install -rf <first module name to be built in the project>
* Option 3: Use the following commands:
** mvn clean install (the build will fail trying to install the jar of one of the modules in the .m2 folder)
** mvn install -rf <name of that first module that failed to have the jar installed>
* Option 4: skip pmd check:
** mvn clean install -Dpmd.skip=true
* Option 5: delete the jar snapshots previously installed in the maven repository folder.
I can't provide a sample project or pom because I was not able to reproduce the issue in a new project. Also, there are other projects with the same characteristcs that does not present the problem, I could not identify any significant difference between them as dependencies and plugins versions, as well as build configuration, are mostly the same.
was:
{*}After ugrading maven from version 3.6.3 to 3.9.4 a few maven projects started failing in the install phase with the error below{*}:
Failed to install artifact xxxxxx:jar:1.1-SNAPSHOT: xxxxx-1.1-SNAPSHOT.jar.3154215231322123456.tmp -> xxxxx-1.1-SNAPSHOT.jar -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install) on project xxxxx: Failed to install artifact xxxxx:jar:1.1-SNAPSHOT: xxxxx-1.1-SNAPSHOT.jar
Caused by: org.apache.maven.plugin.MojoExecutionException:
Caused by: org.eclipse.aether.installation.InstallationException:
Caused by: java.nio.file.AccessDeniedException:
*Command used:* mvn clean install
*All the projects affected have the following characteristics:*
* Multi-modules
* The clean phase is used at least once
* The pmd check is performed
* A jar snapshot of the module already existis in the maven repository folder (.m2)
This is not a blocker issue because *it is still possible to build the projects and install the snapshots* in the local repository if the follwoing options are used:
* Option 1: Avoid using the clean phase. Use only 'mvn install'.
* Option 2: Use the following mvn commands:
** mvn clean
** mvn install -N
** mvn install -rf <first module name to be built in the project>
* Option 3: Use the following commands:
** mvn clean install (the build will fail trying to install the jar of one of the modules in the .m2 folder)
** mvn install -rf <name of that first module that failed to have the jar installed>
* Option 4: skip pmd check:
** mvn clean install -Dpmd.skip=true
* Option 5: delete the jar snapshots previously installed in the maven repository folder.
I can't provide a sample project or pom because I was not able to reproduce the issue in a new project. Also, there are other projects with the same characteristcs that does not present the problem, I could not identify any significant difference between them as dependencies and plugins versions, as well as build configuration, are all the same.
> Fail to install snapshot artifact when clean phase is used
> ----------------------------------------------------------
>
> Key: MINSTALL-194
> URL: https://issues.apache.org/jira/browse/MINSTALL-194
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install
> Affects Versions: 3.1.1
> Environment: Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: C:\Program Files\Maven\apache-maven-3.9.4
> Java version: 11.0.18, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk-11
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Reporter: Candice Tosi Michelon
> Priority: Minor
>
> {*}After ugrading maven from version 3.6.3 to 3.9.4 a few maven projects started failing in the install phase with the error below{*}:
> Failed to install artifact xxxxxx:jar:1.1-SNAPSHOT: xxxxx-1.1-SNAPSHOT.jar.3154215231322123456.tmp -> xxxxx-1.1-SNAPSHOT.jar -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install) on project xxxxx: Failed to install artifact xxxxx:jar:1.1-SNAPSHOT: xxxxx-1.1-SNAPSHOT.jar
> Caused by: org.apache.maven.plugin.MojoExecutionException:
> Caused by: org.eclipse.aether.installation.InstallationException:
> Caused by: java.nio.file.AccessDeniedException:
>
> *Command used:* mvn clean install
>
> *All the projects affected have the following characteristics:*
> * Multi-modules
> * The clean phase is used at least once
> * The pmd check is performed
> * A jar snapshot of the module already existis in the maven repository folder (.m2)
> This is not a blocker issue because *it is still possible to build the projects and install the snapshots* in the local repository if the follwoing options are used:
> * Option 1: Avoid using the clean phase. Use only 'mvn install'.
> * Option 2: Use the following mvn commands:
> ** mvn clean
> ** mvn install -N
> ** mvn install -rf <first module name to be built in the project>
> * Option 3: Use the following commands:
> ** mvn clean install (the build will fail trying to install the jar of one of the modules in the .m2 folder)
> ** mvn install -rf <name of that first module that failed to have the jar installed>
> * Option 4: skip pmd check:
> ** mvn clean install -Dpmd.skip=true
> * Option 5: delete the jar snapshots previously installed in the maven repository folder.
> I can't provide a sample project or pom because I was not able to reproduce the issue in a new project. Also, there are other projects with the same characteristcs that does not present the problem, I could not identify any significant difference between them as dependencies and plugins versions, as well as build configuration, are mostly the same.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)