Kazuhiko Tanaka created GUACAMOLE-2098:
------------------------------------------

             Summary: Building the guacamole client fails because 
guacamole-common-js does not have jsdoc.
                 Key: GUACAMOLE-2098
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-2098
             Project: Guacamole
          Issue Type: Bug
          Components: guacamole-client, guacamole-common-js
    Affects Versions: 1.6.0
         Environment: OS: Ubuntu 22.04.5
JAVA: java-11-openjdk-amd64
mvn: Apache Maven 3.6.3
local npm: {
  npm: '8.3.1',
  node: '12.22.9',
  v8: '7.8.279.23-node.56',
  uv: '1.43.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.18.1',
  modules: '72',
  nghttp2: '1.43.0',
  napi: '8',
  llhttp: '2.1.6',
  http_parser: '2.9.4',
  openssl: '1.1.1m',
  cldr: '40.0',
  icu: '70.1',
  tz: '2025b',
  unicode: '14.0'
}

or

OS: CentOS Stream release 9
JAVA: java-17-openjdk-17.0.15.0.6-3.el9.x86_64
mvn: Apache Maven 3.6.3 (Red Hat 3.6.3-22)
local npm: not installed
            Reporter: Kazuhiko Tanaka


When I run the `mvn package` command on guacamole-client, it stops at building 
`guacamole-common-js`.
When I run it with the `-e -X` option, I get the error `sh: 1: jsdoc: 
Permission denied` (Ubuntu) or `sh: line 1: jsdoc: command not found` (CentOS 
Stream).

On Ubuntu, after installing `jsdoc` (version 4.0.4) using the `npm` command, 
when I run the command the error message changes to `Unknown command-line 
option "".`.

In CentOS, if you run `./npm install jsdoc` in `guacamole-common-js/node/` and 
then run `mvn package` again in guacamole-client, the error changes to 
`node:internal/modules/cjs/loader:1024`. Also, if I update the node-related 
files in `guacamole-common-js/node/` to the latest version, install jsdoc, and 
then run `mvn package`, the same error as in Ubuntu occurs.

Probably `guacamole-common-js` does not contain the required jsdoc and is not 
compatible with the latest jsdoc.

I have confirmed that building guacamole-client 1.5.5 on Ubuntu works fine.
The problem only occurs with 1.6.0.



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

Reply via email to