maloewe-ona

For future reference, it looks like this bug might have been introduced by pull request #2398, and was fixed for 4.11.0 by pull request #2778. I was investigating this some...

> Attaching is not really needed for anything but automatically deploying the produced artifacts to a repository. You can leave attach as false and manually use https://www.mojohaus.org/build-helper-maven-plugin/attach-artifact-mojo.html to attach whatever...

> It make make sense to rename attach to be attachJar then for consistency, but that would be a breaking change. Before doing a full rename, it might be possible...

A few questions: - Should the `LICENSE.txt` file containing the old LGPL license be deleted then? Because some tooling, such as the GitHub UI, still considers it: ...

@lasselindqvist, no sorry I cannot provide a pull request for this. Though as small hint (in case this is useful); the [Maven POM reference](https://maven.apache.org/pom.html#Licenses) recommends that the `` should be...

Thanks for the confirmation! Unfortunately I cannot provide a pull request for this, sorry.

@Reamer, it seems on `master` these files still contain references to `sonar.dependencyCheck.reportPath`. That is not supposed to be a reproach, I am just wondering if you closed this issue here...

Yes, being able to specify the `ClassLoader` to use would probably help (unless `JAXBContext` is used in third-party code you cannot edit). But it would of course be even better...

> We're trying to get a redirect set up in Maven as well, but our current publication point, while working well for the jars, is rejecting it. This has been...