[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Couchman reopened GUACAMOLE-1011:
--------------------------------------

> Unable to build: [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.5.3:single
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1011
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1011
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-client
>    Affects Versions: 1.1.0
>            Reporter: Mechanix
>            Priority: Major
>              Labels: build
>
> I'm unable to build guacamole-client with the provided Dockerfile with my 
> Gitlab CI pipeline:
>  
>  [INFO] guacamole-common 1.1.0 ............................. SUCCESS [ 25.732 
> s]
>  [INFO] guacamole-ext 1.2.0 ................................ SUCCESS [ 9.198 
> s]
>  [INFO] guacamole-common-js 1.2.0 .......................... SUCCESS [ 3.766 
> s]
>  [INFO] guacamole 1.2.0 .................................... SUCCESS [ 26.986 
> s]
>  [INFO] guacamole-auth-cas 1.2.0 ........................... SUCCESS [ 7.943 
> s]
>  [INFO] guacamole-auth-duo 1.2.0 ........................... SUCCESS [ 6.202 
> s]
>  [INFO] guacamole-auth-header 1.2.0 ........................ SUCCESS [ 1.885 
> s]
>  [INFO] guacamole-auth-jdbc 1.2.0 .......................... SUCCESS [ 0.004 
> s]
>  [INFO] guacamole-auth-jdbc-base 1.2.0 ..................... SUCCESS [ 4.175 
> s]
>  [INFO] guacamole-auth-jdbc-mysql 1.2.0 .................... SUCCESS [ 7.118 
> s]
>  [INFO] guacamole-auth-jdbc-postgresql 1.2.0 ............... SUCCESS [ 6.413 
> s]
>  [INFO] guacamole-auth-jdbc-sqlserver 1.2.0 ................ SUCCESS [ 6.678 
> s]
>  [INFO] guacamole-auth-jdbc-dist 1.2.0 ..................... SUCCESS [ 1.567 
> s]
>  [INFO] guacamole-auth-ldap 1.2.0 .......................... SUCCESS [ 11.379 
> s]
>  [INFO] guacamole-auth-openid 1.2.0 ........................ SUCCESS [ 2.986 
> s]
>  [INFO] guacamole-auth-quickconnect 1.2.0 .................. SUCCESS [ 3.011 
> s]
>  [INFO] guacamole-auth-totp 1.2.0 .......................... SUCCESS [ 8.495 
> s]
>  [INFO] guacamole-example 1.2.0 ............................ SUCCESS [ 1.072 
> s]
>  [INFO] guacamole-playback-example 1.2.0 ................... SUCCESS [ 0.582 
> s]
>  [INFO] guacamole-client 1.2.0 ............................. FAILURE [ 5.127 
> s]
>  [INFO] 
> ------------------------------------------------------------------------
>  [INFO] BUILD FAILURE
>  [INFO] 
> ------------------------------------------------------------------------
>  [INFO] Total time: 02:20 min
>  [INFO] Finished at: 2020-04-06T08:43:40Z
>  [INFO] 
> ------------------------------------------------------------------------
>  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.5.3:single 
> (make-source-archive) on project guacamole-client: Failed to create assembly: 
> Error creating assembly archive project: This archives contains unclosed 
> entries. -> [Help 1]
>  [ERROR] 
>  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
>  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>  [ERROR] 
>  [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
>  [ERROR] [Help 1] 
> [http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException]
>  [ERROR] 
>  [ERROR] After correcting the problems, you can resume the build with the 
> command
>  [ERROR] mvn <args> -rf :guacamole-client
>  error building at STEP "RUN /opt/guacamole/bin/build-guacamole.sh 
> "$BUILD_DIR" /opt/guacamole "$BUILD_PROFILE"": error while running runtime: 
> exit status 1
>  time="2020-04-06T08:43:44Z" level=error msg="exit status 1" 
>  Running after_script
>  00:00
>  Uploading artifacts for failed job
>  00:00
>  ERROR: Job failed: exit status 1
> Am I missing something? Thanks



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to