简体   繁体   English

tanukisoft守护程序包装程序和Appassembler Maven插件-如何解决冲突的jar名称?

[英]tanukisoft daemon wrapper and appassembler maven plugin - how to resolve conflicting jar names?

I'm using the http://wrapper.tanukisoftware.com/ wrapper and have two jar files with the same artifactIds and the same version string, but different groupIds. 我使用的是http://wrapper.tanukisoftware.com/包装器,其中有两个jar文件,它们具有相同的artifactIds和相同的版本字符串,但具有不同的groupIds。 Is there any way to prevent losing one of the two jar files when assembling the distribution zip, ie. 有没有什么方法可以防止在组装发行版zip时丢失两个jar文件之一。 use groupId as file name prefix? 使用groupId作为文件名前缀?

Solution was to use the default repository layout instead of the flat one. 解决方案是使用默认的存储库布局,而不是单一的布局。 When using the appassembler (jsw daemon gen) plugin together with the maven-assembly-plugin, one should make sure that one does not resolve the project classpath dependencies using the latter plugin because the appassembler does not know about the copy destination and cannot adjust the classpath accordingly, of course -- just include the lib/ dir output from the appassembler plugin in the final archive. 当将appassembler(jsw daemon gen)插件与maven-assembly-plugin一起使用时,应确保不要使用后一个插件解决项目类路径的依赖关系,因为appassembler不了解复制目标,并且无法调整复制目标。当然,相应的classpath -仅将来自appassembler插件的lib / dir输出包括在最终存档中。 In other words: don't use the dependencySet section in the binary descriptor for classpath dependencies (jars), but rather a fileSet section. 换句话说:对于类路径依赖项(jar),不要在二进制描述符中使用dependencySet部分,而要对fileSet部分使用。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM