RAT-337: Verify compatibility with RAT 0.17

[ottlinger]

Due to the fact that RAT 0.17 introduced many changes (including new config options and a new report layout) I assume the action will have to follow these changes.

Not sure how to (automatically?) test this action, thus I only file this issue.

https://creadur.apache.org/rat
contains the extended docs about the new release, that was promoted yesterday.

[erisu]

I am in the mailing list and been following along with the release and changes.

I just pushed a PR which I am currently working on and testing: #8

It should mostly support RAT 0.17, but it seems there were changes in the output format. I'm investigating this right now to ensure that json.xsl works again, or to find an alternative approach.

[erisu]

I will close this as resolved: https://github.com/erisu/apache-rat-action/releases/tag/v2.0.0

[erisu]

@ottlinger , I wanted to make a note that I created PR #11 to add a GitHub Action Workflow to test itself.

This would remove the need for having a second repo for testing the action.

The only thing that workflow does not test right now is the ability to change versions. I believe the version changing feature should only work for versions that share the same CLI arguments. Since 0.17 was major change and changed the CLI arguments names, that the action used, we couldn't always expect passing tests. We could still test and confirm that the version was changed but silently accept the failure in the test case as we know it could happen if they targeted a breaking version.

Anyways, I will complete this PR. Will then update JIRA to provide documentation about the action. And also wait for the progress of the lifecycle work you talked about prior.

In the meantime, I will also update my project to start using the latest action, using 0.17, just to show it running in an active project.