[
https://issues.apache.org/jira/browse/MINSTALL-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514941#comment-17514941
]
Karl Heinz Marbaise commented on MINSTALL-170:
----------------------------------------------
Have you tried to configure the {{<appendAssemblyId>false</appendAssemblyId>}}
in the maven-assembly-plugin configuration?
> more control over what artifacts to be installed.
> --------------------------------------------------
>
> Key: MINSTALL-170
> URL: https://issues.apache.org/jira/browse/MINSTALL-170
> Project: Maven Install Plugin
> Issue Type: Improvement
> Components: install:install
> Affects Versions: 3.0.0-M1
> Reporter: Ernst Reissner
> Priority: Major
>
> Maybe it is the wrong way to file a feature request but maybe this is the
> best way to come into contact with the development team.
> My problem is that I want to deploy both a jar and a tar.gz file.
> The latter I create with an assembly plugin.
> Unfortunately, the assembly plugin forces the name
> `artifact-version-assId.tar.gz`
> and offers no way to have empty assId.
> The tar.gz is used in another software which strictly speaking requires
> `artifact-version.tar.gz`.
> So I had the simple idea to just move `artifact-version-assId.tar.gz` to
> `artifact-version.tar.gz`
> using exec plugin in a phase before install.
> Well of course i want the install plugin to install now
> `artifact-version.tar.gz` instead of `artifact-version-assId.tar.gz`.
> But the install plugin still wants to use the original artifact.
> My somehow academical question would be how install plugin determines the
> artifact to be installed and to modify that info appropriately.
> It seems to have nothing to do with the packaging as the original tar.gz is
> installed also.
> If I need to define another kind of packaging.... installing other kinds of
> artifacts,
> may I reuse the install plugin????
> Help very much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
