Troubleshooting
In Eclipse, Navigate to Window->Preferences->Maven->Installation. Click on "Add" button and provide maven installation location.
Select User Settings and provide local M2 repo location if it is not configured at default location.
Use -X flag
mvn -X <commands>
Select "Debug output" option in Maven Run\Debug Configuration
Add below loggers in <TIBCO-HOME>\bw\6.x\config\design\logback\logback.xml
<logger name="com.tibco.bw.core.runtime.bw.tests">
<level value="DEBUG"/>
</logger>
<logger name="com.tibco.bw.thor.management.bw.tests">
<level value="DEBUG"/>
</logger> Execute OSGi commands while executing Unit tests by providing commands as below -
mvn test -DosgiCommands=la,lp,bundles
While running the Unit tests, If the application is impaired or stuck, the maven plugin will wait for 2 mins before exiting the process. The default time can be overriden by providing argument as below -
mvn test -DengineStartupWaitTime=5
If you are facing connection or read timeout error while depoying application on Admin. You can override the default timeout value(120000 ms) by providing plugin configuration in pom.xml as below -
<plugin>
<groupId>com.tibco.plugins</groupId>
<artifactId>bw6-maven-plugin</artifactId>
<version>2.7.1</version>
<configuration>
<connectTimeout>240000</connectTimeout>
<readTimeout>240000</readTimeout>
</configuration>
</plugin>Retry count is used to check the application state while starting the application after deployment. The default value is 10. The plugin will check application state after every 10000 ms for the specified retry count to check whether application is in Running state or not. You can override the default retry count by providing plugin configuration in pom.xml as below -
<plugin>
<groupId>com.tibco.plugins</groupId>
<artifactId>bw6-maven-plugin</artifactId>
<version>2.7.1</version>
<configuration>
<retryCount>20</retryCount>
</configuration>
</plugin>Issue : Maven install command failing with error - Error injecting: private org.eclipse.aether.spi.log.Logger org.apache.maven.repository.internal.DefaultVersionResolver.logger
Resolution : The eclipse m2e plugin is embedded with maven version 3.3.3 by default. Please use maven version 3.6.x and above.
Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:properties-maven-plugin:1.0.0:read-project-properties
(execution: default, phase: initialize)
Resolution : This is known behavior in eclipse m2e plugin. Please refer - https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html
You can use eclipse quick fix option to generate lifecycle mapping metadata and then replace <ignore/> action with <execute/>
[exec] An error has occurred. See the log file
[exec] C:\tibco\studio\4.0\eclipse\configuration\1605543239240.log
[exec] Result: 13
Resolution : Check Java version. It should be 64-Bit. Java 1.8 (64-Bit) is recommended.
Failure to find com.tibco.plugins:com.tibco.bw.palette.shared:jar:6.1.100 in https://repo.maven.apache.org/maven2 was cached in the local repository
Resolution : Please refer -
- https://support.tibco.com/s/article/Error-Missing-artifact-com-tibco-plugins-com-tibco-bw-palette-shared-jar-6-1-100-after-generating-for-application
- Please check settings.xml as mentioned in #396
Resolution : The plugin is using "user-agent: Java/1.8.0_41" (via apache commons) which is rejected by Gitlab. You can override that by executing maven goal as below -
mvn clean install -Dhttp.agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36"
Installation Error - HTTP Server Unknown HTTP Response Code (301):http://download.eclipse.org/releases/luna/artifacts.xml
Resolution : The eclipse update site http://download.eclipse.org/releases/luna/ is no longer available, which is causing failure to install Maven plugin versions prior to 2.9.0.
After extracting the installer zip, please replace http://download.eclipse.org/releases/luna/ with https://download.eclipse.org/eclipse/updates/4.4/ in build.xml.