[ 
https://issues.apache.org/jira/browse/MINSTALL-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MINSTALL-116.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Robert Scholte

When installing (or deploying) an artifact, is must have a predictable path, 
otherwise Maven can't download it in the future. Based on the groupId, 
artifactId, version and type (which is translated to a file-extension) and 
optional classifier Maven can build that path.

How would a {{<dependency>}} look like if a custom final name was used?

{quote}
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.
{quote}
Attached artifacts *must* use a classifier to recognize the different 
attachments.

> 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)

Reply via email to