commit | 74d28d8948f8c1ff6f9e805c5510b46b5ad5c0b3 | [log] [tgz] |
---|---|---|
author | Marat Abrarov <abrarov@gmail.com> | Tue Oct 13 16:34:56 2020 +0300 |
committer | GitHub <noreply@github.com> | Tue Oct 13 09:34:56 2020 -0400 |
tree | 8f1767b9472d24642cc60b2bc5a2e4ea6a63a707 | |
parent | 1e35164b797e3bf1f95116b9b977e6282ffb0b26 [diff] |
[MEAR-267] - Fixed detection if JAR module is included into classpath of particular EAR module manifest (#19) * [MEAR-267] - Fixed detection if EAR JAR module is included into classpath of particular EAR module manifest * [MEAR-267] - Fixed detection of need of modification of Class-Path entry of EAR module manifest * [MEAR-267] - Performance optimization for the case when EAR module manifest has no Class-Path entry * [MEAR-267] - Integration tests * [MEAR-267] - The same rules applied to modification of Class-Path manifest entry as used for removal of JAR modules from EAR modules * [MEAR-267] - Fixed formatting of JavaDoc in tests * [MEAR-267] - Test for the case when unpacking of EJB JARs is turned on * [MEAR-267] - Renamed test method parameters and rephrased / fixed formatting of JavaDoc, inlined simple single-line code. * [MEAR-267] - Minor code style fix. * [MEAR-267] - JavaDoc simplified. * [MEAR-267] - Test for "dirty" build. * [MEAR-267] - Fixed modification of Class-Path entry of manifest of EAR modules when doing "dirty" build, i.e. when element with desired path already exists in target manifest Class-Path entry * [MEAR-267] - Support of JDK 11+ in integration tests
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.[MEAR-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.