[
https://issues.apache.org/jira/browse/HADOOP-19824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Fabbri resolved HADOOP-19824.
-----------------------------------
Fix Version/s: 3.5.1
Resolution: Fixed
This is fixed in trunk. Note I filed HADOOP-19850 to follow up on this when we
move to maven 4+, so we can use the offficially-supported property to determine
the root of the project.
> Build failure: Could not find resource '${repo.root}' ...
> ---------------------------------------------------------
>
> Key: HADOOP-19824
> URL: https://issues.apache.org/jira/browse/HADOOP-19824
> Project: Hadoop Common
> Issue Type: Bug
> Components: hadoop-common
> Affects Versions: 3.5.0
> Reporter: Aaron Fabbri
> Assignee: Aaron Fabbri
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.5.1
>
>
> When trying to run `spotbugs` target on a submodule from the repo root, I'm
> getting a failure to resolve ${repo.root}. Reproduction:
>
> {{mvnd clean}}
> {{mvnd clean compile -pl hadoop-tools/hadoop-aws -am}}
> {{mvnd -pl hadoop-tools/hadoop-aws -am spotbugs:spotbugs}}
> {{...}}
> {{Could not find resource
> '${repo.root}/dev-support/findbugs-exclude-global.xml'}}
> Am I expected to `cd` into the submodule folder first? Do we really need this
> `directory-maven-plugin` which is supposed to compute `repo.root` for us? Why
> not just use relative paths (e.g. ../../)? I'm not very skilled with maven
> but this seems brittle.
> This repo.root thing was introduced for global excludes as part of a spotbugs
> upgrade in HADOOP-19731.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
