* use provided scope for maven dependencies
As the maven-plugin-plugin suggests, dependencies to the maven runtime
should be in provided scope.
This gets rid of the according warning which was written during build.
Before Maven 3.9, plexus-utils was injected in the classpath at runtime.
As of Maven 3.9 this is not the case anymore which broke the plugin due
to a usage of said dependency. The only usage is replaced by a visitor
to copy files.
Closes#30542
Signed-off-by: Michael Warnecke <WarneckeMichael@web.de>
* Guides need to see maven's Log class
Signed-off-by: Michael Warnecke <WarneckeMichael@web.de>
---------
Signed-off-by: Michael Warnecke <WarneckeMichael@web.de>
* Use a valid SemVer format for the SNAPSHOT version
* Update pom.xml
* Update pom.xml
---------
Co-authored-by: Stian Thorgersen <stianst@gmail.com>
Co-authored-by: Stian Thorgersen <stian@redhat.com>
* Allow exposing some initial provider config options via web site
Co-authored-by: Stian Thorgersen <stian@redhat.com>
Closes#10571
* Include type to provider options, and hide build-icon column as it's not relevant
Co-authored-by: stianst <stianst@gmail.com>
