maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boaz Lev (JIRA)" <>
Subject [jira] [Commented] (MINSTALL-116) Attached artifacts installed with default name, only one is actually installed
Date Wed, 09 Sep 2015 21:43:46 GMT


Boaz Lev commented on MINSTALL-116:

The maven-assembly-plugin configuration and the descriptors are O.K. their <id> is properly
configured, yet ignored as configured in pom.xml, and the expected artifacts are generated
in the target: and was not expected? ONLY was installed, and with different

> Attached artifacts installed with default name, only one is actually installed
> ------------------------------------------------------------------------------
>                 Key: MINSTALL-116
>                 URL:
>             Project: Maven Install Plugin
>          Issue Type: Bug
>          Components: install:install
>    Affects Versions: 2.5.2
>            Reporter: Boaz Lev
>            Assignee: Robert Scholte
> InstallMojo.execute() calls (for every attached artifact) to 
> installer.install( attached.getFile(), attached, localRepository );
> The source file name is based on finalName, but destination file name is based on the
localRepository.pathOf(File) method, which in the org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout
implementation returns a result based on artifactId, version etc.
> In short, this means that if the artifactId is "X" and the version is "0.0.1-SNAPSHOT"
then an artifact with a name "" will be installed as ""
> Since all attached artifacts are installed with the default name, in case there are more
than on attached artifacts - only the last is actually installed, all others are getting lost
in the process.
> I would expect that any attached artifact would be installed using it's finalName, exactly
as it is on the target folder.

This message was sent by Atlassian JIRA

View raw message