Getting the following error while trying to run steady on steady-cli

Describe the bug This problem occurs when I run steady on steady-cli. I didn’t find steady-cli-3.2.3, so I used steady-cli-3.2.0 the command ‘java -jar steady-cli-3.2.0-jar-with-dependencies.jar -goal app’ the error [main] [ERROR] e.steady.shared.util.StopWatch - [287797] [00.059 ms] Failed: Application context is required to execute goal [APP] Exception in thread "main" org.eclipse.steady.goals.GoalConfigurationException: Application context is required to execute goal [APP] at org.eclipse.steady.goals.AbstractAppGoal.prepareExecution(AbstractAppGoal.java:107) at org.eclipse.steady.goals.BomGoal.prepareExecution(BomGoal.java:57) at org.eclipse.steady.goals.AbstractGoal.start(AbstractGoal.java:418) at org.eclipse.steady.goals.AbstractGoal.execute(AbstractGoal.java:253) at org.eclipse.steady.goals.AbstractGoal.executeSync(AbstractGoal.java:247) at org.eclipse.steady.cli.VulasCli.main(VulasCli.java:99)

steady-custom.properties file I have edit the <GROUP>, <ARTIFACT> and <VERSION> of the application to be analyzed and my workspace token

steady-cli folder The application code (java, class or JAR files) and all application dependencies (JAR files) In the app folder

I have read the Java source code, but still can’t find the problem and how to fix it. Can you please teach me how to solve this problem，thank you！

[11111821]

Hi @serenaponta Thank you very much for your help. I succeeded. Thank you！

[serenaponta]

Hi @11111821,

when using the steady-cli the app folder must contain both the application code and the dependencies. Then the configuration of vulas.core.app.appPrefixes or vulas.core.app.appJarNames is used to discriminate between the two. Looking at the log of the steady-cli you provided above, I think you have the spring-boot-demo application in the app folder (as the DirAnalyzer found only Java and Class files) but the dependencies are not present (as usually happens in Maven projects). The way to proceed is to add the dependencies, e.g., simply running mvn dependency:copy-dependencies and configuring the package prefix (as you did).

I also tested the demo-zookeeper module: I run the mvn command above to get the dependencies within the app folder and configured vulas.core.app.appPrefixes = com.xkcoding and got the expected 77 dependencies. The first alternative you used for the appPrefixes configuration should also work but if you don’t have dependencies under com.xkcoding the one I used makes it simpler 😃