[GitHub] [camel-k] dmarrazzo opened a new issue, #3779: Improve the user feedback when the integration kit fails

[GitBox <gi...@apache.org>]

dmarrazzo opened a new issue, #3779:
URL: https://github.com/apache/camel-k/issues/3779

   Hi all, this is a follow up of the issue #3775 
   In that issue the Integration Kit was failing with the following error message
   
   ```yaml
     failure:
       reason: 'failure while building project: exit status 1'
       recovery:
         attempt: 5
         attemptMax: 5
   ```
   
   Investigating the issue, we reached the conclusion that the root cause was the presence of two conflicting dependencies:
   
   ```
     - camel:micrometer
     - mvn:org.apache.camel.quarkus:camel-quarkus-microprofile-metrics
   ```
   
   The **goal of the current issue** is to improve the user experience when a similar problem make the integration kit fail.
   In fact, from a user perspective the error was too generic and there was no way to retrieve the build process error.
   
   Thank you


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-k] tadayosi commented on issue #3779: Improve the user feedback when the integration kit fails

[GitBox <gi...@apache.org>]

tadayosi commented on issue #3779:
URL: https://github.com/apache/camel-k/issues/3779#issuecomment-1293043787

   In the next release Camel K 1.11.0 we will add some dependency validations at operator and cli (see #3640), which will give you a bit better error message on a single invalid dependency.
   
   However, in your case the problem is with a conflicting set of dependencies and probably it's not easy to validate those combinations beforehands. So, to extract a better error message from those failures the operator would need to parse the Maven build log for the build kit and identify what's the reason for failure. (Just a note for developers.)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-k] squakez commented on issue #3779: Improve the user feedback when the integration kit fails

[GitBox <gi...@apache.org>]

squakez commented on issue #3779:
URL: https://github.com/apache/camel-k/issues/3779#issuecomment-1293119848

   I am not sure what is the `mvn` execution error trace here, but, in general, we should try to include it in the error status.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-k] squakez closed issue #3779: Improve the user feedback when the integration kit fails

[GitBox <gi...@apache.org>]

squakez closed issue #3779: Improve the user feedback when the integration kit fails
URL: https://github.com/apache/camel-k/issues/3779


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org