[
https://issues.apache.org/jira/browse/SOLR-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-8876:
---------------------------
Description:
morphline configs we use in our contrib tests have {{importCommands}} that
look like this...
{noformat}
importCommands : ["org.kitesdk.**", "org.apache.solr.**"]
{noformat}
...but under java9 these tests fail with errors like...
{noformat}
No command builder registered for COMMAND_NAME
{noformat}
...because of how morphlines attempts to locate classes matching those globs --
this type of classpath scanning does not work in java9.
workaround is to only use fully qualified command class names in
{{importCommands}} declaration. No other (obviuos) java9 problems seem to
exist with solr's use of morphlines (based on current test coverage)
was:
They fail with: "No command builder registered for name".
I added an assume through SOLR-8874.
Component/s: contrib - morphlines-core
contrib - morphlines-cell
Summary: Morphlines tests fail with Java 9 due to morphline
"importCommands" attempting to resolve classname globs in config files (was:
Morphlines tests fail with Java 9 (Jigsaw))
tweaked summary/description to reflect current state of situation.
(should be updated/refined more -- if/when we commit patch -- to be more user
centric)
> Morphlines tests fail with Java 9 due to morphline "importCommands"
> attempting to resolve classname globs in config files
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-8876
> URL: https://issues.apache.org/jira/browse/SOLR-8876
> Project: Solr
> Issue Type: Bug
> Components: contrib - MapReduce, contrib - morphlines-cell, contrib
> - morphlines-core
> Reporter: Uwe Schindler
> Labels: Java9
> Attachments: SOLR-8876.patch
>
>
> morphline configs we use in our contrib tests have {{importCommands}} that
> look like this...
> {noformat}
> importCommands : ["org.kitesdk.**", "org.apache.solr.**"]
> {noformat}
> ...but under java9 these tests fail with errors like...
> {noformat}
> No command builder registered for COMMAND_NAME
> {noformat}
> ...because of how morphlines attempts to locate classes matching those globs
> -- this type of classpath scanning does not work in java9.
> workaround is to only use fully qualified command class names in
> {{importCommands}} declaration. No other (obviuos) java9 problems seem to
> exist with solr's use of morphlines (based on current test coverage)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
