Skip to content

JupiterConfigProvider fails with ClassNotFoundExecption #747

@dnestoro

Description

@dnestoro

Describe the bug
After we solved problem with leaking dependencies (avoid adding duplicated entries on classpath) in some cases some classes couldn't be found because users didn't explicitly add necessary dependencies on classpath. If we can't find classes on the classpath, we should ignore registering their properties (the same as we did here).

To Reproduce

Described in this issue: #745

Expected behavior
If the classpath contains all necessary dependencies, the test should pass.
If there is missing dependencies we should ignore ClassNotFoundException in config providers (later, if that was really missing, we will fail with the proper error message)

System Info (please complete the following information):

  • OS: [all]
  • GraalVM Version [all]
  • Java Version [all]
  • Plugin version [native-gradle-plugin:0.11.0]

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions