Closed aornatovskyy closed 3 years ago
This is thornier than it seems. I found this comment: https://github.com/mycila/license-maven-plugin/issues/36#issuecomment-33956023
And I'm starting to think option number 2 might be the way out of these woods. (Did you ask if Nexus team have other ideas?) You could try option 2 by:
mvn install
that jar in your local maven repo.license-maven-plugin
in the parent pom.xmllicense-maven-plugin
to refer to the header.txt in that jar via a classpath, like: <header>classpath:/org/sonatype/repository/header.txt</header>
If that works, we could publish the license header jar, and all the format projects could re-use it.
will not be relevant after migrating source code helm to nexus
Ticket: https://issues.sonatype.org/browse/NEXUS-24473
License header check works: https://app.circleci.com/pipelines/github/sonatype-nexus-community/nexus-repository-helm/344/workflows/ca296651-6077-4bd7-b57c-9aca1e5f8d10/jobs/380/steps