Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.0.0-M1
-
None
Description
When using the CLI, it currently throws the below error:
org.apache.nifi.toolkit.cli.api.CommandException: Error executing command 'pg-export' : java.lang.ClassNotFoundException: Provider for jakarta.ws.rs.client.ClientBuilder cannot be found at org.apache.nifi.toolkit.cli.impl.command.nifi.AbstractNiFiCommand.doExecute(AbstractNiFiCommand.java:65) at org.apache.nifi.toolkit.cli.impl.command.AbstractPropertyCommand.execute(AbstractPropertyCommand.java:74) at org.apache.nifi.toolkit.cli.impl.command.CommandProcessor.processCommand(CommandProcessor.java:248) at org.apache.nifi.toolkit.cli.impl.command.CommandProcessor.processGroupCommand(CommandProcessor.java:229) at org.apache.nifi.toolkit.cli.impl.command.CommandProcessor.process(CommandProcessor.java:184) at org.apache.nifi.toolkit.cli.CLIMain.runSingleCommand(CLIMain.java:145) at org.apache.nifi.toolkit.cli.CLIMain.main(CLIMain.java:72) Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider for jakarta.ws.rs.client.ClientBuilder cannot be found at jakarta.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:75) at org.apache.nifi.toolkit.cli.impl.client.nifi.impl.JerseyNiFiClient.<init>(JerseyNiFiClient.java:98) at org.apache.nifi.toolkit.cli.impl.client.nifi.impl.JerseyNiFiClient$Builder.build(JerseyNiFiClient.java:345) at org.apache.nifi.toolkit.cli.impl.client.NiFiClientFactory.createClient(NiFiClientFactory.java:169) at org.apache.nifi.toolkit.cli.impl.client.NiFiClientFactory.createClient(NiFiClientFactory.java:59) at org.apache.nifi.toolkit.cli.impl.command.nifi.AbstractNiFiCommand.doExecute(AbstractNiFiCommand.java:62) ... 6 more Caused by: java.lang.ClassNotFoundException: Provider for jakarta.ws.rs.client.ClientBuilder cannot be found at jakarta.ws.rs.client.FactoryFinder.find(FactoryFinder.java:163) at jakarta.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:62) ... 11 more
Not sure which exact change caused this but it's likely related to some dependency management improvements we did.
Attachments
Issue Links
- is fixed by
-
NIFI-11703 Upgrade Spring Framework to version 6
- Resolved