Need to update pom.xml under be-contribution.

Version Information

What is the expected behavior?

The store jar should be created after updating pom.xml with BE_HOME.

What is the actual behavior?

The jar creation failed as shown below.
C:\Share\Repo\be-contribution\store\redis>mvn clean install
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.tibco.businessevents:redis🫙1.0
[WARNING] 'dependencies.dependency.systemPath' for com.tibco.businessevents:cep-external-tibxml-sdk:jar refers to a non-existing file C:\Share\630\BE_630_v33\be\6.3\lib\ext\tibco\com.tibco.tibcoxml.xml.sdk.eclipse_5.60.100.002.jar @ com.tibco.businessevents:contribution:1.0.0, C:\Share\Repo\be-contribution\pom.xml, line 84, column 25
[WARNING] 'dependencies.dependency.systemPath' for com.tibco.businessevents:cep-external-tibxml-util:jar refers to a non-existing file C:\Share\630\BE_630_v33\be\6.3\lib\ext\tibco\com.tibco.tibcoxml.util.eclipse_5.60.100.001.jar @ com.tibco.businessevents:contribution:1.0.0, C:\Share\Repo\be-contribution\pom.xml, line 91, column 25
[WARNING] 'dependencies.dependency.systemPath' for com.tibco.businessevents:cep-external-tibxml-io:jar refers to a non-existing file C:\Share\630\BE_630_v33\be\6.3\lib\ext\tibco\com.tibco.tibcoxml.io.eclipse_5.60.100.001.jar @ com.tibco.businessevents:contribution:1.0.0, C:\Share\Repo\be-contribution\pom.xml, line 98, column 25
[WARNING] 'dependencies.dependency.systemPath' for com.tibco.businessevents:cep-external-tibcoxml-wsdl:jar refers to a non-existing file C:\Share\630\BE_630_v33\be\6.3\lib\ext\tibco\com.tibco.tibcoxml.xml.ws.wsdl.eclipse_5.60.100.001.jar @ com.tibco.businessevents:contribution:1.0.0, C:\Share\Repo\be-contribution\pom.xml, line 126, column 25
[WARNING] 'dependencies.dependency.systemPath' for com.tibco.businessevents:tpcl-antlr:jar refers to a non-existing file C:\Share\630\BE_630_v33\be\6.3\lib\ext\tpcl\antlr-3.2.jar @ line 90, column 16
[WARNING] 'dependencyManagement.dependencies.dependency.systemPath' for com.tibco.businessevents:cep-external-tibxml-sdk:jar refers to a non-existing file C:\Share\630\BE_630_v33\be\6.3\lib\ext\tibco\com.tibco.tibcoxml.xml.sdk.eclipse_5.60.100.002.jar @ com.tibco.businessevents:contribution:1.0.0, C:\Share\Repo\be-contribution\pom.xml, line 84, column 25
[WARNING] 'dependencyManagement.dependencies.dependency.systemPath' for com.tibco.businessevents:cep-external-tibxml-util:jar refers to a non-existing file C:\Share\630\BE_630_v33\be\6.3\lib\ext\tibco\com.tibco.tibcoxml.util.eclipse_5.60.100.001.jar @ com.tibco.businessevents:contribution:1.0.0, C:\Share\Repo\be-contribution\pom.xml, line 91, column 25
[WARNING] 'dependencyManagement.dependencies.dependency.systemPath' for com.tibco.businessevents:cep-external-tibxml-io:jar refers to a non-existing file C:\Share\630\BE_630_v33\be\6.3\lib\ext\tibco\com.tibco.tibcoxml.io.eclipse_5.60.100.001.jar @ com.tibco.businessevents:contribution:1.0.0, C:\Share\Repo\be-contribution\pom.xml, line 98, column 25
[WARNING] 'dependencyManagement.dependencies.dependency.systemPath' for com.tibco.businessevents:cep-external-tibcoxml-wsdl:jar refers to a non-existing file C:\Share\630\BE_630_v33\be\6.3\lib\ext\tibco\com.tibco.tibcoxml.xml.ws.wsdl.eclipse_5.60.100.001.jar @ com.tibco.businessevents:contribution:1.0.0, C:\Share\Repo\be-contribution\pom.xml, line 126, column 25
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] -------------------< com.tibco.businessevents:redis >-------------------
[INFO] Building redis 1.0
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.070 s
[INFO] Finished at: 2023-02-07T16:54:45+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project redis: Could not resolve dependencies for project com.tibco.businessevents:redis🫙1.0: The following artifacts could not be resolved: com.tibco.businessevents:cep-external-tibxml-sdk🫙6.3, com.tibco.businessevents:cep-external-tibxml-util🫙6.3, com.tibco.businessevents:cep-external-tibxml-io🫙6.3, com.tibco.businessevents:cep-external-tibcoxml-wsdl🫙6.3, com.tibco.businessevents:tpcl-antlr🫙6.3: Could not find artifact com.tibco.businessevents:cep-external-tibxml-sdk🫙6.3 at specified path C:\Share\630\BE_630_v33\be\6.3\lib\ext\tibco\com.tibco.tibcoxml.xml.sdk.eclipse_5.60.100.002.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

In BE 6.3.0, the version number from jars have been removed so I have to update the jar name acc. then it worked.
It is better to update the pom.xml file acc.
pom.zip

Inspect pom.xml under be-contribution, especially the dependency paths reported in the Maven output, and compare them with the BE 6.3.0 jar names described in the issue and attached pom.zip. Run mvn clean install from the store directory; done means the store jar is created without unresolved dependency errors.