[
https://issues.apache.org/jira/browse/MINSTALL-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873861#comment-17873861
]
Tamas Cservenak commented on MINSTALL-198:
------------------------------------------
If maven-embedder here means "programmatically invoking MavenCli from inside
Maven..." then this is no-go.
> maven-embedder: second install-file overrides first one
> -------------------------------------------------------
>
> Key: MINSTALL-198
> URL: https://issues.apache.org/jira/browse/MINSTALL-198
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install-file
> Reporter: Franz-Josef Färber
> Priority: Major
>
> I am using the maven {{install:install-file}} goal with both cases: Jar-Files
> containing a pom-file or not, as described in
> https://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html .
> While on the command-line the following works:
> {code:bash}
> mvn install:install-file -Dfile=somefile.jar -DgroupId=somegroup
> -DartifactId=someartefact -Dversion=1.0.0 -Dpackaging=jar -DgeneratePom=true
> mvn install:install-file -Dfile=someotherfile-containing-a-pom-file.jar
> {code}
> using maven-embedder, it does not work: On the second install:install-file
> goal, the {{-DgroupId}}, {{-Dartifact}} parameters from the first call are
> still somehow present and trigger overriding the first Jar file in the local
> maven repo.
> MRE:
> https://github.com/fjf2002/78041113-maven-embedder-maven-install-plugin-bug-second-install-file-overrides-first-one
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
