-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not initialize POS mapping loader if mapping is disabled #1511
Comments
reckart
added a commit
that referenced
this issue
Dec 31, 2022
- Do not initialize/configure mapper if the mapped feature is disabled
reckart
added a commit
that referenced
this issue
Jun 10, 2023
reckart
added a commit
that referenced
this issue
Jun 10, 2023
reckart
added a commit
that referenced
this issue
Jun 10, 2023
reckart
added a commit
that referenced
this issue
Jun 10, 2023
…e-POS-mapping-loader-if-mapping-is-disabled #1511 - Do not initialize POS mapping loader if mapping is disabled
reckart
added a commit
that referenced
this issue
Jun 13, 2023
* main: (59 commits) #1560 - Upgrade dependencies #1560 - Upgrade dependencies #1560 - Upgrade dependencies #1560 - Upgrade dependencies #1560 - Upgrade dependencies #1565 - Option to replace illegal characters in XMI files #1565 - Option to replace illegal characters in XMI files #1560 - Upgrade dependencies #1560 - Upgrade dependencies #1511 - Do not initialize POS mapping loader if mapping is disabled Update README.md #1560 - Upgrade dependencies No issue. Switch SCM to https [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release dkpro-core-2.3.1 No issue. Switch SCM to https [maven-release-plugin] rollback the release of dkpro-core-2.3.1 [maven-release-plugin] prepare release dkpro-core-2.3.1 #1561 - Upgrade dependencies #1561 - Upgrade dependencies ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do not initialize POS mapping loader if mapping is disabled, e.g. in CoNLL2006Reader, but likely in other places as well.
The text was updated successfully, but these errors were encountered: