[
https://issues.apache.org/jira/browse/RAT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847637#comment-17847637
]
Claude Warren commented on RAT-381:
-----------------------------------
[~pottlinger] , The change for this fix is to add a filtered resource file
(Version.properties) into which maven inserts the version number. This is then
read by Version.java into a static variable.
Does this impact the release process? My concern is that if we build RC1 then
the RC1 will be in the version string. So after we approve RC1 we have to
change the version and rebuild the code for a release. Will this work within
the current release process?
> Add accurate version info to the Command line parsing.
> ------------------------------------------------------
>
> Key: RAT-381
> URL: https://issues.apache.org/jira/browse/RAT-381
> Project: Apache Rat
> Issue Type: Sub-task
> Components: Client - cli, configuration
> Affects Versions: 0.16.1
> Reporter: Claude Warren
> Assignee: Claude Warren
> Priority: Minor
>
> The output from the client help shows the version number pattern, not the
> actual version number.
> This change is to figure out how to store the maven version number within the
> jar so that we can report it in help and other associated places.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
