[
https://issues.apache.org/jira/browse/MINSTALL-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737631#comment-14737631
]
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: a.zip and b.zip.What was not expected?
ONLY b.zip was installed, and with different name...
> Attached artifacts installed with default name, only one is actually installed
> ------------------------------------------------------------------------------
>
> Key: MINSTALL-116
> URL: https://issues.apache.org/jira/browse/MINSTALL-116
> 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 "a.zip" will be installed as
> "X-0.0.1-SNAPSHOT.zip"
> 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
(v6.3.4#6332)
