[PR] Bump org.slf4j:slf4j-simple from 2.0.11 to 2.0.12 [creadur-rat]
dependabot[bot] opened a new pull request, #213: URL: https://github.com/apache/creadur-rat/pull/213 Bumps org.slf4j:slf4j-simple from 2.0.11 to 2.0.12. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@creadur.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (RAT-362) plugin: .gitignore not correctly applied
[ https://issues.apache.org/jira/browse/RAT-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned RAT-362: Assignee: Jean-Baptiste Onofré > plugin: .gitignore not correctly applied > > > Key: RAT-362 > URL: https://issues.apache.org/jira/browse/RAT-362 > Project: Apache Rat > Issue Type: Bug >Reporter: Arnout Engelen >Assignee: Jean-Baptiste Onofré >Priority: Minor > > When I have a Maven project checked out in the directory '/foo', and I have a > file called 'foo.md' in the root of that project, ignoring it by putting a > '/foo.md' entry in the .gitignore file does not work. > It is unclear whether this is an issue in the plugin or in de codeowners > gitignore-reader dependency: the plugin is passing relative filenames (i.e. > 'foo.md') to GitIgnoreFileSet#isIgnoredFile , but the API docs on that method > don't make it too clear whether that is intended to accept absolute > filenames, relative filename, or both. > In this scenario, it seems to take the relative filename 'foo.md' and remove > the project base directory '/foo' from it, leaving '/.md' (which then of > course does not match the 'foo.md' from the .gitignore). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RAT-362) plugin: .gitignore not correctly applied
[ https://issues.apache.org/jira/browse/RAT-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814345#comment-17814345 ] Jean-Baptiste Onofré commented on RAT-362: -- Thanks for the report, I will take a look. > plugin: .gitignore not correctly applied > > > Key: RAT-362 > URL: https://issues.apache.org/jira/browse/RAT-362 > Project: Apache Rat > Issue Type: Bug >Reporter: Arnout Engelen >Assignee: Jean-Baptiste Onofré >Priority: Minor > > When I have a Maven project checked out in the directory '/foo', and I have a > file called 'foo.md' in the root of that project, ignoring it by putting a > '/foo.md' entry in the .gitignore file does not work. > It is unclear whether this is an issue in the plugin or in de codeowners > gitignore-reader dependency: the plugin is passing relative filenames (i.e. > 'foo.md') to GitIgnoreFileSet#isIgnoredFile , but the API docs on that method > don't make it too clear whether that is intended to accept absolute > filenames, relative filename, or both. > In this scenario, it seems to take the relative filename 'foo.md' and remove > the project base directory '/foo' from it, leaving '/.md' (which then of > course does not match the 'foo.md' from the .gitignore). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RAT-362) plugin: .gitignore not correctly applied
Arnout Engelen created RAT-362: -- Summary: plugin: .gitignore not correctly applied Key: RAT-362 URL: https://issues.apache.org/jira/browse/RAT-362 Project: Apache Rat Issue Type: Bug Reporter: Arnout Engelen When I have a Maven project checked out in the directory '/foo', and I have a file called 'foo.md' in the root of that project, ignoring it by putting a '/foo.md' entry in the .gitignore file does not work. It is unclear whether this is an issue in the plugin or in de codeowners gitignore-reader dependency: the plugin is passing relative filenames (i.e. 'foo.md') to GitIgnoreFileSet#isIgnoredFile , but the API docs on that method don't make it too clear whether that is intended to accept absolute filenames, relative filename, or both. In this scenario, it seems to take the relative filename 'foo.md' and remove the project base directory '/foo' from it, leaving '/.md' (which then of course does not match the 'foo.md' from the .gitignore). -- This message was sent by Atlassian Jira (v8.20.10#820010)
