[
https://issues.apache.org/jira/browse/RAT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847735#comment-17847735
]
Claude Warren commented on RAT-381:
-----------------------------------
The version number in the jar will be the same as the one in the generated
file and the same as the value specified in the pom. I assume you change
the pom and regenerate the jar for release. If that is the case then the
solution work as it is.
Switching to reading the manifest.mf will not work for source code tests
and any case where the jar is not present. Also, finding the.proper jar
requires knowing the version or. Just picking the first one on the path.
> 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
> Attachments: OpenPGP_signature.asc
>
>
> 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)
