For https://github.com/gravitee-io/gravitee-management-webui , the "Nexus Staging" Process is a maven build, and it fails because some files, if not all, in the node/ folder do not have the license header expected by the maven license plugin configuration.
Expected Behavior
While running the "Nexus staging" Process in the new CICD, the maven build should not fail becasue of missing headers in files located in the node folder.
Current Behavior
The Nexus Staging fails because of the above descirbed issue
Possible Solution
I have fixed the issue on git branch 3.5.x, by adding the ccc exclude filter in the pom.xml, see here.
This exclude filter should be added on all git branch, at least on support branch for versions higher than 3.6.0 : so at least on 3.6.x branch.
I believe it would not hurt anything, to add this exclude filter on all git branches.
Steps to Reproduce (for bugs)
VERY IMPORTANT: DO NOT TRY AND REPRODUCE THIS BUG WITHOUT CONTACTING DEVOPS TEAM : THIS OPERATION IMPACTS IMMUTABLE NEXUS PUBLIC SERVICE GRAVITEE PRODUCTS
For https://github.com/gravitee-io/gravitee-management-webui , the "Nexus Staging" Process is a maven build, and it fails because some files, if not all, in the
node/
folder do not have the license header expected by the maven license plugin configuration.Expected Behavior
While running the "Nexus staging" Process in the new CICD, the maven build should not fail becasue of missing headers in files located in the
node
folder.Current Behavior
The Nexus Staging fails because of the above descirbed issue
Possible Solution
I have fixed the issue on git branch
3.5.x
, by adding the ccc exclude filter in thepom.xml
, see here.This exclude filter should be added on all git branch, at least on support branch for versions higher than 3.6.0 : so at least on
3.6.x
branch.I believe it would not hurt anything, to add this exclude filter on all git branches.
Steps to Reproduce (for bugs)
Context
Your Environment
3.5.8-SNAPSHOT
maven:3.6.3-openjdk-11