[MINSTALL-170] more control over what artifacts to be installed.

[jira-importer]

Ernst Reissner opened MINSTALL-170 and commented

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.

---

Affects: 3.0.0-M1

[jira-importer]

Karl Heinz Marbaise commented

Have you tried to configure the <appendAssemblyId>false</appendAssemblyId> in the maven-assembly-plugin configuration?

[jira-importer]

Ernst Reissner commented

@KHM: yes! i managed far later and it works...
Still I would be curious about how the install plugin determines what in fact to install.
I cannot figure out the mechanism and there is no documentation, well I found no documentation on this subject at all.
Maybe a good idea just to add documentation.

@SJ: which feedback you need from me?

[jira-importer]

Slawomir Jaranowski commented

Thanks ErnstReissner - for your response.

As I understood your problem was resolved by change configuration of assembly plugin and can be closed.

from plugin site:  https://maven.apache.org/plugins/maven-install-plugin/

install:install is used to automatically install the project's main artifact (the JAR, WAR or EAR), its POM and any attached artifacts (sources, javadoc, etc) produced by a particular project.

main artifact is current project artifact - it is generated by plugin using during packagin phase

attached artifacts - are additional artifacts produced by another plugins like assemby

So install plugin only use list of artifacts to install prepared by another plugins.