Maven build hangs indefinitely when building project EAR

Maven build hangs indefinitely when building project EAR

book

Article ID: KB0073502

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition 5.6

Description

When an attempt is made to build the project EAR using the maven install or package commands, the build hangs indefinitely. The console shows.. 

[INFO] Scanning for projects...
[INFO] 
[INFO] --------------------< com.tibco.be:BEProject >---------------------
[INFO] Building BEProject 1.0.0
[INFO] --------------------------------[ ear ]---------------------------------
[INFO] 
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources-1) @ BEProject ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Using 'null' encoding to copy filtered properties files.
[INFO] skip non existing resourceDirectory C:\Users\user\Documents\BEProject\src\main\resources
[INFO] 
[INFO] --- be-maven-plugin:5.6.1:becompile (default-becompile-1) @ BEProject ---
Build project EAR file BEProject-1.0.0.ear in progress..
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized.  Will retry after the state location is initialized.
org.eclipse.m2e.logback.configuration: Logback config file: C:\TIBCO\be\5.6\studio\workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration\logback.1.12.0.20190529-1916.xml
org.eclipse.m2e.logback.configuration: Initializing logback

****************************************************************************
	TIBCO BusinessEvents 5.6.1.159 (2021-01-24)
	Using arguments :-core buildEar -p C:/Users/user/Documents/BEProject -o C:/Users/user/Documents/BEProject/target/BEProject-1.0.0.ear -x 
	Copyright(c) 2004-2019 TIBCO Software Inc. All rights reserved.
	
****************************************************************************
From this point on, there is no additional output printed to the console, and the process is hung.

 

Environment

Windows Platform

Resolution

This may occur when the Term and Alias values for two (or more) events are the same. This can happen in some cases where project directories have been renamed and Studio/Eclipse refactoring does not complete properly.

To resolve this, inspect your *.event definition's Advanced tab under the Declarations section. Ensure each event has unique values for Term and Alias. 

Issue/Introduction

Maven goals such as 'install' or 'package' may indefinitely hang if two or more event definitions have the same values for Term and Alias.
Powered by Wolken Software