Peter Palaga
Peter Palaga
Could you please try to reproduce with the latest version (currently 2.0.0) of the plugin?
Please run with `-X` find the effective configuration of the plugin in the console output and paste it here.
No, what you posted is a stack trace, not the config. Please find the last occurrence of `[DEBUG] Configuring mojo 'org.codehaus.mojo:license-maven-plugin:` in the console output and paste everything starting there...
Might some `add-third-party` expert (e.g. @digulla, @nfalco79, @elballa) please have a look at the data above and try to explain why the mojo attempts to download `https://repo.maven.apache.org/maven2/io/reactivex/rxnetty-servo/0.4.9/rxnetty-servo-0.4.9-third-party.properties`. Please eventually also...
Might some `add-third-party` expert (e.g. @digulla, @nfalco79, @elballa) please state whether the above behavior is expected?
What would happen with the `verbose` Mojo parameter?
A PR with an integration test is welcome. In the meantime, you may want to consider using `com.mycila:license-maven-plugin` that adds no clutter to the license header. [1] https://github.com/mycila/license-maven-plugin
It would be highly welcome if a volunteer could extend [update-file-header-test-mojo integration test](https://github.com/mojohaus/license-maven-plugin/tree/master/src/it/update-file-header-test-mojo) to reproduce the named scenario: * Add an HTML file to the test project * Add an...
A PR with an integration test would be welcome.
> In a perfect world, everyone would move to SPDX identifiers in their POMs immediately I do not think this is ever going to happen. Having researched a bit, I...