[jira] [Resolved] (LOG4J2-2836) No way to distinguish release candidate tags from release versions

["Matt Sicker (Jira)" <ji...@apache.org>]

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

Matt Sicker resolved LOG4J2-2836.
---------------------------------
      Assignee: Volkan Yazici
    Resolution: Fixed

Volkan handled this when updating the Scala build to work with the automated release process.

> No way to distinguish release candidate tags from release versions
> ------------------------------------------------------------------
>
>                 Key: LOG4J2-2836
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2836
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Scala API
>            Reporter: Matt Sicker
>            Assignee: Volkan Yazici
>            Priority: Major
>
> In the {{create-distributions.sh}} script, this currently assumes that a tagged release will not have a {{-rcN}} suffix which prevents the source archive from being created. These distribution scripts will need to be refactored a bit to ensure that the tag and release version are not conflated.



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