You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/08/11 16:02:00 UTC

[jira] [Created] (SLING-11530) Jenkins Maven Repository Deployment due to violating rat checks in multimodule build

Konrad Windszus created SLING-11530:
---------------------------------------

             Summary: Jenkins Maven Repository Deployment due to violating rat checks in multimodule build
                 Key: SLING-11530
                 URL: https://issues.apache.org/jira/browse/SLING-11530
             Project: Sling
          Issue Type: Bug
          Components: CI
            Reporter: Konrad Windszus
            Assignee: Konrad Windszus


Even after the fixes of SLING-11401 the following error can still be experienced for multi-module builds:

{code}
[INFO] --- apache-rat-plugin:0.14:check (rat-check) @ sling-maven-plugin.reactor ---
[...
[WARNING] Files with unapproved licenses:
  local-snapshots-dir/org/apache/sling/maven-metadata.xml.sha1
  local-snapshots-dir/org/apache/sling/maven-metadata.xml
  local-snapshots-dir/org/apache/sling/maven-metadata.xml.md5
...
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:53 min
[INFO] Finished at: 2022-08-11T15:53:48Z
[INFO] ------------------------------------------------------------------------
[INFO] [jenkins-event-spy] Generated /home/jenkins/jenkins-agent/workspace/odules_sling-maven-plugin_master/jdk_1.8_latest@tmp/withMavene7346aae/maven-spy-20220811-155155-4511382858674172539989.log
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.14:check (rat-check) on project sling-maven-plugin.reactor: Too many files with unapproved license: 33 See RAT report in: /home/jenkins/jenkins-agent/workspace/odules_sling-maven-plugin_master/jdk_1.8_latest/target/rat.txt -> [Help 1]
{code}

(e.g. in https://ci-builds.apache.org/job/Sling/job/modules/job/sling-maven-plugin/job/master/119/console).

The reason is that the files to be deployed are staged from other modules in the reactor root directory first, and only afterwards the RAT check is being performed.

As we cannot use the target file for the staged artifacts either (as being cleaned after being populated) we need to rely on a directory which is excluded by default from RAT checks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)