Add log discriminator to separate log file when modernized plugin

[jonesbusy]

Redirect all build logs to specific logger to avoid polluting the console logs and will simplify debugging, also ensure batch mode and remove transfer progress

Will create for example one log file per plugin and one for tool

Testing done

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[sridamul]

ProcessBuilder.start(): pid: 42512, dir: E:\plugin-modernizer-tool\test-plugins\test-plugin-1, cmd: "cmd.exe" 
java.lang.RuntimeException: ProcessBuilder.start() debug
        at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1147)
        at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1089)
        at java.base/java.lang.Runtime.exec(Runtime.java:681)
        at org.apache.maven.shared.utils.cli.Commandline.execute(Commandline.java:390)
        at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLineAsCallable(CommandLineUtils.java:232)
        at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:172)
        at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:147)
        at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:125)
        at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:92)
        at org.apache.maven.shared.invoker.DefaultInvoker.executeCommandLine(DefaultInvoker.java:131)
        at org.apache.maven.shared.invoker.DefaultInvoker.execute(DefaultInvoker.java:97)
        at io.jenkins.tools.pluginmodernizer.core.impl.MavenInvoker.invokeGoals(MavenInvoker.java:115)
        at io.jenkins.tools.pluginmodernizer.core.impl.MavenInvoker.invokeGoal(MavenInvoker.java:41)
        at io.jenkins.tools.pluginmodernizer.core.impl.PluginModernizer.start(PluginModernizer.java:27)
        at io.jenkins.tools.pluginmodernizer.cli.Main.run(Main.java:63)
        at picocli.CommandLine.executeUserObject(CommandLine.java:2030)
        at picocli.CommandLine.executeHelpRequest(CommandLine.java:2016)
        at picocli.CommandLine.executeHelpRequest(CommandLine.java:1987)
        at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2272)
        at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
        at picocli.CommandLine.execute(CommandLine.java:2174)
        at io.jenkins.tools.pluginmodernizer.cli.Main.main(Main.java:25)
[INFO] Scanning for projects...

I am getting this runtime exception and no logs are generated in the logs directory for plugins, it only contains modernizer.log file.

[jonesbusy]

Apparently it's caused by the --debug flag. I will check

[jonesbusy]

This should be better now @sridamul

• Console log is clean by default
• modernizer.log contains the same data but with timestamps and formatted logs
• <plugin.log> contains specific logs for plugin build using Markers

The --debug only change what is displayed related to console and application log

[sridamul]

Hey @jonesbusy Everything looks great and perfectly works fine in my local environment, FYI still the runtime exception arises when --debug flag is enabled. Thanks!

[jonesbusy]

Hey @jonesbusy Everything looks great and perfectly works fine in my local environment, FYI still the runtime exception arises when --debug flag is enabled. Thanks!

My feeling is that is just a log of the java.lang.ProcessBuilderthat print some "normal" exception when DEBUG level is raised. So I think it's safe to merge. But I can investigate later