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

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2025/01/08 13:00:00 UTC

[jira] [Comment Edited] (OAK-11319) Enable "rat" profile with GHA

    [ https://issues.apache.org/jira/browse/OAK-11319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911067#comment-17911067 ] 

Julian Reschke edited comment on OAK-11319 at 1/8/25 12:59 PM:
---------------------------------------------------------------

The reason why the rat check was disabled was that many developers (well, at least one) keep log files, diffs etc in the checked out repo.

This is now impossible.


was (Author: reschke):
The reason why the rat check was disabled was that many developers (well, at least one) keep log files, diffs etc in the checked out repo.

This is now impossible.

> Enable "rat" profile with GHA
> -----------------------------
>
>                 Key: OAK-11319
>                 URL: https://issues.apache.org/jira/browse/OAK-11319
>             Project: Jackrabbit Oak
>          Issue Type: Task
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: 1.74.0
>
>
> As the {{rat}} profile is used in Jenkins (https://github.com/apache/jackrabbit-oak/blob/437375bdc9eb5207b6019587f9a21d6d018ff9bf/Jenkinsfile#L66), it should be active in GHA as well. 
> However maybe we should reconsider to enable the rat check with the regular build (unconditionally) as the overhead is really low.



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