Conversation
OpenNLP moved its issue tracking from JIRA to GitHub Issues. Update the remaining places that point contributors and users at JIRA: - pom.xml: issueManagement now points to GitHub Issues - PR template: ask for a linked GitHub issue instead of an OPENNLP-XXXX key - distribution README footer: report issues on GitHub, link release notes - opennlp-distr: drop the apache-release jira-report profile and the issuesFixed assembly fileSet that packaged its output - dev manual: point contributors to GitHub, keep old tickets as history - .asf.yaml: drop jira_options; autolink_jira stays so historic OPENNLP-XXXX references in commits keep linking
krickert
reviewed
Sep 20, 2026
| are very welcome. If you want to contribute please contact us on the mailing list | ||
| or comment on the jira issue <link xlink:href="https://issues.apache.org/jira/browse/OPENNLP-48">OPENNLP-48</link>. | ||
| or open an issue on <link xlink:href="https://github.com/apache/opennlp/issues">GitHub</link> | ||
| (see also the historical issue <link xlink:href="https://issues.apache.org/jira/browse/OPENNLP-48">OPENNLP-48</link>). |
Contributor
There was a problem hiding this comment.
Such an old bug, looking forward to watching it die. This will be added to the javadoc effort.
krickert
approved these changes
Sep 20, 2026
krickert
left a comment
krickert
left a comment
Contributor
There was a problem hiding this comment.
I'll be sure to clear out the documentation issues sometime soon (release or not)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpenNLP moved its issue tracking from JIRA to GitHub Issues. This updates the remaining places that point contributors and users at JIRA.
pom.xml:issueManagementnow points to https://github.com/apache/opennlp/issues (this ends up in the POMs published to Maven Central).github/PULL_REQUEST_TEMPLATE.md: asks for a linked GitHub issue (e.g.Fixes #1234) instead of anOPENNLP-XXXXkeyopennlp-distr/README_FOOTER.html: tells users to report issues on GitHub and links to the GitHub release notes for fixed issuesopennlp-distr: removes theapache-releaseprofile that ranmaven-changes-plugin:jira-report(needed-DjiraVersion), and theissuesFixedfileSet in the bin assembly that packaged its outputcoref.xml,parser.xml): points contributors to GitHub Issues and keeps the old tickets as historical references.asf.yaml: removesjira_options.autolink_jirastays so the historicOPENNLP-XXXXreferences in commit messages and PR titles still link to the (read-only) JIRALeft as is on purpose: historic
OPENNLP-XXXXreferences in code comments and the provenance links in test/data resources (e.g.abb_PT.xml,origin-training-data.txt).Note:
.asf.yamlis only read from the default branch, so that change is just for consistency with main.