You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@logging.apache.org by vy...@apache.org on 2022/05/09 10:57:44 UTC

[logging-log4j2] 01/03: INFRA-23225 Exclude log4j-bom from deployments.

This is an automated email from the ASF dual-hosted git repository.

vy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git

commit 311e8399549bbae5881e0e84f35e481270e2e8f0
Author: Volkan Yazıcı <vo...@yazi.ci>
AuthorDate: Mon May 9 12:57:08 2022 +0200

    INFRA-23225 Exclude log4j-bom from deployments.
---
 .github/workflows/build.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 9b676feece..e14acf5aae 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -112,8 +112,10 @@ jobs:
         shell: bash
         # `package install:install deploy:deploy` goal is needed to deploy without configuring the plugin in the POM.
         # For details see: https://maven.apache.org/plugins/maven-gpg-plugin/examples/deploy-signed-artifacts.html
+        # INFRA-23225 `log4j-bom` is excluded due to 401 errors.
         run: |
           ./mvnw \
+            -pl '!log4j-bom' \
             --show-version --batch-mode --errors --no-transfer-progress \
             -Dgpg.skip=true \
             -DskipTests=true \