Component REST API doesn't work on Java 9 #51
Comments
|
Also reported to Reflections, as it seems to be a problem with their library: ronmamo/reflections#202 |
JohnDaws
pushed a commit
that referenced
this issue
Mar 12, 2018
* Update version number to 2.5.0-SNAPSHOT * Update Swagger to 3.4.5 * Update dependency versions * Update OpenCSV version * Change from using the Reflections library to FastClasspathScanner, which is both faster and supports Java 9. Fixes #51. * New servlet to retrieve default values (e.g. default ContentExtractor) * Fix Issue #49 (Plankton should have default content extractor selected) * Upgrade to Elasticsearch 5.6.4 * Rename UimaContentExtractor to PlainTextContentExtractor * Add null check in to prevent collection reader hanging if metadata is missing * Move away from IOUtils, which can cause freezing on large documents - Fixes Issue #50 * Remove deprecated APIs * Add NCA copyright * Add NCA copyright * Add NCA copyright * Add NCA copyright * Add new Vulnerability type to type system * New annotators: CVE, Epoch Time, IPv6 and Lenient URL * New collection readers: CSV Folder, MBOX, SQL Cell, SQL DB Cell, SQL Row * New consumers: Elastic-Kibana, Gremlin * Add copyright statement * Update version * Remove use of deprecated function * Update dependency versions * Update dependency version * Update test resources * Update dependencies * Fix issue with child nodes in JSoup * Dependency updates * Wrap Stream in a try-resource block so that it is closed after use. I believe this would have been closed when it went out of scope anyway, but the approach here ensures that is the case. * Wrap ResultSet in a try-resource block so that it is closed after use. * Wrap Stream in a try-resource block so that it is closed after use. * Wrap Stream in a try-resource block so that it is closed after use. * Wrap ResultSet in a try-resource block so that it is closed after use. * Wrap resources in a try-resource block so that it is closed after use. * Bug fix for cases where a file path is used rather than a URI * Wrap ResultSet in a try-resource block so that it is closed after use. * Ensure SQL resources are closed * Change client variable to be of type TransportClient * Remove incorrect Javadoc * Make variable final
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The component REST API - which returns a list of available components such as annotators - doesn't work on Java 9. This appears to be an issue with the Reflections API, which is giving the following warning when running on Java 9:
Running the same JAR on Java 8 doesn't produce this warning. The component API seems to return a null/empty object, which is therefore breaking the Plankton interface as well.
The text was updated successfully, but these errors were encountered: