TIBCOSoftware / bw6-plugin-maven

Plug-in Code for Apache Maven and TIBCO ActiveMatrix BusinessWorks™
Other
65 stars 78 forks source link

Size of Ear generated using Mvn set up is very less compared to create Archive file process #527

Open Manikanta532 opened 3 years ago

Manikanta532 commented 3 years ago

Maven Plugin version: 2.7.1 Maven version: C:\Windows\system32>mvn --version Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: C:\tibco\sb-cep\10.6\sdk\mvn\bin.. Java version: 11.0.7, vendor: Oracle Corporation, runtime: C:\tibco\sb-cep\10.6\jdk Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Product : Either of TIBCO ActiveMatrix Businessworks 6 OR TIBCO Businessworks Container edition BW6 Product version: BW 6.6.1 HF002 Component: Either of Maven Eclipse Plugin or Maven build plugin

using Maven build plugin

Steps to reproduce the issue:

  1. I have taken the existing project , right clicked on the project and clicked generate pom for the application. 2.It created the pom.xml file under the Sharedmodule, Jms dependency module, under application module and main application. 3.I ran the Maven build with goal of install on all dependencies first the the main application, able to see the ear under target folder and under the .m2 but if i extract it i dont see the procecsses of the code. Size of ear differs with the size of the one got generated using the studio.
  2. I could see one more application with extension.parentis getting created even though i remove .parent in the artifact id name while generating pom
  3. Kindly help on what am i missing to get the correct ear generated.

Additional environment details if any: In local laptop

Describe the results you received: Ear size is not proper

Describe the results you expected: Exact ear needs to be generated . Capture

Additional information you deem important (e.g. issue happens only occasionally):

vpawar-tibco commented 3 years ago

Hi @Manikanta532 , Maven plugin generates a new project with .parent extension and this is expected behaviour. Please check EAR zip contents and review the pom files.

Manikanta532 commented 3 years ago

Hi @vpawar-ai ,

Thank you for the response.

we have a Sharedmodule and custom jmsprovider for the application, I have added them as dependencies in the pom file of the .module and in the pom of the application i have added dependency for the .module, i see this is given proper, am facing issue while building the custom.jms provider i.e solace.

I see this is causing the issue with the ear file size difference, It would be helpful if you suggest anything based on the error, attached.

Thank you in advance. Correct me if anything is given wrong as per my description in the pom maven_error.txt custom_jms_provider

vpawar-tibco commented 3 years ago

Hi @Manikanta532 Based on attached logs, it failed to compile the custom jms driver code because of missing dependencies. You will need to add pom dependency entries for missing dependencies in custom jms driver project pom.xml. Please refer #139