smengcl commented on code in PR #4070: URL: https://github.com/apache/ozone/pull/4070#discussion_r1053756152
########## pom.xml: ########## @@ -233,7 +233,7 @@ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xs <checkstyle.version>9.3</checkstyle.version> <surefire.fork.timeout>1200</surefire.fork.timeout> <aws-java-sdk.version>1.12.261</aws-java-sdk.version> - <frontend-maven-plugin.version>1.12.0</frontend-maven-plugin.version> + <frontend-maven-plugin.version>1.12.1</frontend-maven-plugin.version> Review Comment: I suspect that `npx` somehow lost track of its `node_modules` root directory path in the process. Might be a bug in `frontend-maven-plugin` or `npx` or `npm` or `pnpm`. I don't know too much about those nodejs build system so I can't be sure without digging even further. At least I see tons of `lib` directory for each nodejs module: ``` ozone$ find . -name lib ... ./hadoop-ozone/recon/target/node/node_modules/npm/node_modules/npm-bundled/node_modules/npm-normalize-package-bin/lib ./hadoop-ozone/recon/target/node/node_modules/npm/node_modules/npm-bundled/lib ./hadoop-ozone/recon/target/node/node_modules/npm/node_modules/nopt/lib ./hadoop-ozone/recon/target/node/node_modules/npm/lib ... ``` If this is the case merely creating the empty directory won't do much either. Need to debug this somehow. Or search for solutions. -- 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]
