Add classLoader to project-build-plugin validation context

[alexsuter]

No description provided.

[ivy-edp]

👍 🥇

[alexsuter]

@weissreto just that you get the full overview. the classloader which is needed by the validators needs to be provided by the framework/context. in the project-build-plugin only the plugin itself knows the classpath of the project. in the lsp-validation-endpoints there is still JavaRuntime.of(project).getClassLoader() in use. We already should differ in the core between a compile classpath and a runtime classpath. Later on, we can switch from a classloader to a yandex based index.

[ivy-rew]

@weissreto just that you get the full overview. the classloader which is needed by the validators needs to be provided by the framework/context. in the project-build-plugin only the plugin itself knows the classpath of the project. in the lsp-validation-endpoints there is still JavaRuntime.of(project).getClassLoader() in use. We already should differ in the core between a compile classpath and a runtime classpath. Later on, we can switch from a classloader to a yandex based index.

Thanks for sharing the context among the team 🤝 🥇

[alexsuter]

I think this is the right approach. But not working because we only have ivy-runtime.jar on the compile classpath and all dependency from thirdparty-libs are currently missing.
we need to wait with them until we publish the official jars with it's dependencies to maven repository.