egeria: [BUG] Release 3.4 doesn`t work when running it as JAR file
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
While building the new Egeria 3.4 Release with the following command line:
mvn -B -U -Dmaven.test.skip -Drat.skip=true -Dmaven.javadoc.skip=true -DuseMavenCentral package
As a result of build process i get a JAR, which i try to run, it crashed with ModuleNotFound. I`ve done some research and found out that there is some issue with local build process. Maybe maven forget to compile smth, idk.
But if i will run Egeria as java application (without building jar) with that command line below:
{javaPath}\java.exe -XX:TieredStopAtLevel=1 -noverify -Dspring.output.ansi.enabled=always "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA 2021.2.2\lib\idea_rt.jar=63544:C:\Program Files\JetBrains\IntelliJ IDEA 2021.2.2\bin" -Dcom.sun.management.jmxremote -Dspring.jmx.enabled=true -Dspring.liveBeansView.mbeanDomain -Dspring.application.admin.enabled=true -Dfile.encoding=UTF-8 @C:\Users\{user}\AppData\Local\Temp\idea_arg_file907069212 org.odpi.openmetadata.serverchassis.springboot.OMAGServerPlatform
Everything works fine.
Expected Behavior
I expect that both way to run Egeria platform will work the same way
Steps To Reproduce
Described in the current behavior
Environment
- Egeria: 3.4 Release
- OS: Windows 10
- Java: liberica 11.0.13
- Additional connectors and integration: CruxDB Egeria connector
Any Further Information?
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 33 (24 by maintainers)
Here’s a pre-built version of the XT connector jar that is now built against the 3.4 Egeria release – might be worth testing using this connector jar with your startup sequence just to confirm whether the problem still exists, or if it is resolved (suggesting that indeed connectors must be recompiled against the release even if just specifying dependencies as
provided…)https://oss.sonatype.org/content/repositories/snapshots/org/odpi/egeria/egeria-connector-xtdb/3.4-SNAPSHOT/egeria-connector-xtdb-3.4-20211206.101230-6-jar-with-dependencies.jar
Based on what you confirm, I can then decide whether to release the 3.4 version of the XT connector as-is to address this (rather than waiting on further details on the other exception that we mentioned a couple weeks back on a dev call – though perhaps the two are related?)
Another observation - the exception is occuring from Governance Engine OMAS. Do you need to run this OMAS? If not you could disable it? And I suspect you don’t see other issues (though it’s still a bug)