bnd-resolver-maven-plugin: Redirect resolver log to Maven plugin log

[kwin]

Currently the bnd-resolver-maven-plugin calls

bnd/biz.aQute.resolve/src/biz/aQute/resolve/RunResolution.java

Line 83 in 72b494a

public static RunResolution resolve(Project project, Processor actualProperties,

via

bnd/biz.aQute.resolve/src/biz/aQute/resolve/Bndrun.java

Line 103 in 72b494a

public String resolve(boolean failOnChanges, boolean writeOnChanges) throws Exception {

and via

bnd/maven-plugins/bnd-resolver-maven-plugin/src/main/java/aQute/bnd/maven/resolver/plugin/ResolverMojo.java

Line 163 in 72b494a

String result = run.resolve(failOnChanges, writeOnChanges);

As the passed resolverLogger is null, a new temporary one is created in

bnd/biz.aQute.resolve/src/biz/aQute/resolve/RunResolution.java

Line 112 in 72b494a

ResolverLogger logger = resolverLogger == null ? ResolverLogger.newLogger(actualProperties, false)

which just logs to a tmp file which is deleted at exit and otherwise just emits debug message via SLF4J (

bnd/biz.aQute.resolve/src/biz/aQute/resolve/ResolverLogger.java

Line 100 in 72b494a

logger.debug(msg);

)

For Maven plugins the one being returned via https://maven.apache.org/ref/3.9.15/maven-plugin-api/apidocs/org/apache/maven/plugin/Mojo.html#getLog() should be used instead through a wrapper derived from

bnd/biz.aQute.resolve/src/biz/aQute/resolve/ResolverLogger.java

Line 22 in 72b494a

public class ResolverLogger implements LogService, AutoCloseable {

.