smengcl commented on PR #8037:
URL: https://github.com/apache/ozone/pull/8037#issuecomment-2741882511
It looks to me `ozone-dist` is misbehaving during `mvn clean install -Pdist
-DskipTests -e -Dmaven.javadoc.skip=true`.
It looks to be interpreting some variables in `enable-ozone-plugin.sh` to an
unwanted hard-coded path:
```bash
$ rg "/Users/smeng/repo/ozone-pr/hadoop-ozone/dist"
compose/ozone/ranger-plugin/enable-ozone-plugin.sh
24: if [ -f "/Users/smeng/repo/ozone-pr/hadoop-ozone/dist/pom.xml" ]
26: propertyValue=`grep "^${propertyName}[ \t]*="
/Users/smeng/repo/ozone-pr/hadoop-ozone/dist/pom.xml | awk -F= '{ sub("^[
\t]*", "", $2); sub("[ \t]*$", "", $2); print $2 }'`
64:if [ "/Users/smeng/repo/ozone-pr/hadoop-ozone/dist" = "." ]
67:elif [ "/Users/smeng/repo/ozone-pr/hadoop-ozone/dist" = ".." ]
113:PROJ_INSTALL_DIR=`(cd /Users/smeng/repo/ozone-pr/hadoop-ozone/dist ;
pwd)`
```
Take line 24 for example, in the source code it should be:
```bash
if [ -f "${file}" ]
```
My question: Why would this bash script file even be changed during `dist`
copy? Is there some maven plugin accidentally changing this? Do you happen to
have any clue @adoroszlai ?
---
My steps for verification:
1. Switch to PR branch, launch maven build
2. Switch to `compose/ozone/`, install plugin and start Docker compose
cluster
```bash
./ranger-plugin-setup.sh
docker compose -f docker-compose.yaml -f docker-compose.ranger.yaml up -d
```
3. Log in to Ranger Web UI with credentials: `admin`/`rangerR0cks!`
4. Attempt to use CLI:
```
ozone fs -ls ofs://om/
```
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
