| [sw360-dev] current maven based deploy currently not OK |
Hi, I have repeated builds now, on different platforms and I suspect that current master has a problem with our old vagrant (see below). Old because I suspect most of you are on docker, right? I think it is not showing up at other occasions, because we do not do mvn -P deploy in any of our other builds, just in the vagrant-based build? Executing '-P deploy' brings the error below, just to let you know. Kind regards, Michael [INFO] rest .............................................. SUCCESS [0.180s] [INFO] authorization-server .............................. FAILURE [1:25.324s] [INFO] resource-server ................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 7:04.600s [INFO] Finished at: Thu Feb 22 12:13:53 UTC 2018 [INFO] Final Memory: 105M/526M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:1.5.8.RELEASE:repackage (default) on project authorization-server: Execution default of goal org.springframework.boot:spring-boot-maven-plugin:1.5.8.RELEASE:repackage failed: Source must refer to an existing file, got /opt/apache-tomcat-7.0.67/deploy/authorization.war -> [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/PluginExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :authorization-server
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail