commit | 23ab0535647d38efee5defe56b458b93d65a4ad3 | [log] [tgz] |
---|---|---|
author | Tamas Cservenak <tamas@cservenak.net> | Tue Jul 19 15:58:26 2022 +0200 |
committer | GitHub <noreply@github.com> | Tue Jul 19 15:58:26 2022 +0200 |
tree | bdf2f8f884f7336d48f111dc7ff2c12f4280911b | |
parent | 00080521a8f66524f121b92a7f8cd3169645f7b0 [diff] |
[MINSTALL-160] Generated POM is not installed if original POM exists (#36) 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.
You have found a bug or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:
git diff --check
before committing.[MINSTALL-XXX] - Subject of the JIRA Ticket Optional supplemental description.
mvn -Prun-its verify
to assure nothing else was accidentally broken.If you plan to contribute on a regular basis, please consider filing a contributor license agreement.
For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA. In this case, it is appropriate to start the first line of a commit with ‘(doc)’ instead of a ticket number.