commit | 87995c6e2484f3a6476fc29c600c294ede849f22 | [log] [tgz] |
---|---|---|
author | Markus Spann <sman81@outlook.de> | Sun Jul 24 15:47:20 2022 +0200 |
committer | Slawomir Jaranowski <s.jaranowski@gmail.com> | Mon Jul 25 10:43:45 2022 +0200 |
tree | 105cbbfbc999c394cb45715ec819cfe079b5cfbd | |
parent | a803fbf1cd8bc26bf8947a6e544ca4b6b3d5e7be [diff] |
[JXR-170] NullPointerException while parsing Java 15 multi-line String source - Add support for parsing sources with Java 15 multi-line Strings - Add JUnit test case - Implement toString on class BaseType - Require non-null name on BaseType construtor - Prevent construction of types with null name - Add version to maven-enforcer-plugin plugin to prevent failure of integration test JXR-143_nofork
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.[JXR-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.