Skip to content

[MINSTALL-160] Generated POM is not installed if original POM exists - #36

Merged
cstamas merged 2 commits into
masterfrom
MINSTALL-160
Jul 19, 2022
Merged

[MINSTALL-160] Generated POM is not installed if original POM exists#36
cstamas merged 2 commits into
masterfrom
MINSTALL-160

Conversation

@cstamas

@cstamas cstamas commented Jul 18, 2022

Copy link
Copy Markdown
Member

When using generatePom=true with install-file Mojo, it will despite
this copy existing POM if it is found embedded in JAR (and if it
was built with Maven, it will find it).

The generatePom should reuse POM values embedded from JAR
but should generate (and install) new "empty POM" instead.


https://issues.apache.org/jira/browse/MINSTALL-160

When using `generatePom=true` with install-file Mojo, it will despite
this copy existing POM if it is found embedded in JAR (and if it
was built with Maven, it will find it).

The generatePom should reuse POM values embedded from JAR
but should generate (and install) new "empty POM" instead.
@cstamas
cstamas requested review from gnodet, hboutemy and michael-o July 18, 2022 12:55
@cstamas cstamas self-assigned this Jul 18, 2022
@wilx

wilx commented Jul 18, 2022

Copy link
Copy Markdown

Works for me. 👍

@cstamas
cstamas merged commit 23ab053 into master Jul 19, 2022
@cstamas
cstamas deleted the MINSTALL-160 branch July 19, 2022 13:58
@jira-importer

Copy link
Copy Markdown

Resolve #326

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants