Getting the following error while trying to run steady on gradle

[tr0nand]

Describe the bug
Unable to run steady on gradle due to the following issue -

Could not resolve all files for configuration ':classpath'.
Could not resolve org.eclipse.steady:plugin-gradle:3.2.3.
Required by:
project :
> Could not resolve org.eclipse.steady:plugin-gradle:3.2.3.
> Could not parse POM https://repo.maven.apache.org/maven2/org/eclipse/steady/plugin-gradle/3.2.3/plugin-gradle-3.2.3.pom
> Could not find org.eclipse.steady:root:3.2.3.
Searched in the following locations:
- https://repo.maven.apache.org/maven2/org/eclipse/steady/root/3.2.3/root-3.2.3.pom
- https://plugins.gradle.org/m2/org/eclipse/steady/root/3.2.3/root-3.2.3.pom
> Could not resolve org.eclipse.steady:plugin-gradle:3.2.3.
> Could not parse POM https://plugins.gradle.org/m2/org/eclipse/steady/plugin-gradle/3.2.3/plugin-gradle-3.2.3.pom
> Could not find org.eclipse.steady:root:3.2.3.

[serenaponta]

Hello @123tarunanand ,

thanks for reporting the issue. The gradle client is failing as the artifact root-3.2.3.pom is currently not published to Maven Central.
We will evaluate how to fix it, in the meantime the plugin-maven client remains the most used and tested client and the steady-cli could be used as temporary solution (https://eclipse.github.io/steady/user/tutorials/java_cli/#scanning-java-apps-with-the-cli).

Thanks for your understanding.

[henrikplate]

Though .flattened-pom.xml is generated for module plugin-gradle, as for all other modules, it does not replace the original pom.xml due to the fact the module has packaging pom. This behavior can be changed through configuration setting updatePomFile.

[henrikplate]

@123tarunanand The Gradle problem should be resolved with release 3.2.4, which does not reference the parent POM any more. Please let us know whether it works for you.

[tr0nand]

Yes. That seems to work