Open balintbozan opened 4 years ago
Please share the project. If this cannot be shared on Github, please open an SR and provide the SR details here.
Hi, see and attached project. The project name is MavenBuildDemo but the artifact name is MavenDemo. The target folder of the application has a created ear which does not contain any jar file.
There is an other bug in the 2.7 release: The target folder of the module has a jar but the file name is same as the project name, not the configured artifact name. As I remember it wasn't problem when I opened the issue (2.5 release)
Maven Plugin version: 2.6
Maven version: Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: c:\Projects\apache-maven\bin.. Java version: 1.8.0_241, vendor: Oracle Corporation, runtime: c:\Program Files\Java\jdk1.8.0_241\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Product : TIBCO BusinessStudio for BusinessWorks
Product version: 2.5.2 V67 2020-03-05
Component: Maven build plugin
Steps to reproduce the issue:
Additional environment details if any: Windows 10
Describe the results you received: The ear in the application target folder only has the META-INF folder
Describe the results you expected: The ear in the application target folder needs to have resource folder, manifest.json, and 3 jars
Additional information you deem important (e.g. issue happens only occasionally): Jars of the modules (or shared modules, or xpath custom function) are generated and located in the target folder. However, if the artifactId and the project name is different than the generated jar will be missing from the ear.
mvn_package_log.txt