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

Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2023/12/02 00:07:00 UTC

[jira] [Resolved] (LOG4J2-3000) Move to CI-friendly versions in Maven

     [ https://issues.apache.org/jira/browse/LOG4J2-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker resolved LOG4J2-3000.
---------------------------------
    Resolution: Fixed

This has been addressed by now as we have an automated release preparation process now.

> Move to CI-friendly versions in Maven
> -------------------------------------
>
>                 Key: LOG4J2-3000
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3000
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: Volkan Yazici
>            Assignee: Volkan Yazici
>            Priority: Minor
>
> Starting with Maven 3.5.0-beta-1, one can use the {{$\{revision}}} as placeholder for the version in pom files. This enhancement will make the version updates a breeze (i.e., {{\-Drevision=6.6.6}}) and trigger a single line change in the root pom rather than touching every pom file out there in modules.
> Note that {{flatten\-maven\-plugin}} needs to be employed at install & deploy stages. For details see [Maven CI Friendly Versions|https://maven.apache.org/maven-ci-friendly.html].



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