I followed the instruction mentioned on
https://camel.apache.org/camel-quarkus/latest/first-steps.html to run
simple example, but its throwing error while running

$ mvn clean compile quarkus:dev

Error:

[INFO] Scanning for projects...

[INFO]

[INFO] -----< org.apache.camel.quarkus:camel-quarkus-examples-rest-json
>------

[INFO] Building Camel Quarkus :: Examples :: Rest Json 1.0.0-M2

[INFO] --------------------------------[ jar
]---------------------------------

[INFO]

[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @
camel-quarkus-examples-rest-json ---

[INFO]

[INFO] --- directory-maven-plugin:0.3.1:highest-basedir (directories) @
camel-quarkus-examples-rest-json ---

[INFO] Highest basedir set to: /Users/imran/testcamel/rest-json

[INFO]

[INFO] --- groovy-maven-plugin:2.1.1:execute (sanity-checks) @
camel-quarkus-examples-rest-json ---

[INFO]
------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
------------------------------------------------------------------------

[INFO] Total time:  1.654 s

[INFO] Finished at: 2020-01-02T00:51:04+01:00

[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (sanity-checks) on
project camel-quarkus-examples-rest-json: Execution sanity-checks of goal
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute failed: Impossible to
read the text content from
file:/Users/imran/testcamel/rest-json/tooling/scripts/validate-dependencies.groovy:
/Users/imran/testcamel/rest-json/tooling/scripts/validate-dependencies.groovy
(No such file or directory) -> [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/PluginExecutionException

Reply via email to