You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2019/11/13 08:26:57 UTC

[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #405: core: avoid referencing application classes in bean build items and loading them in core build processors

lburgazzoli edited a comment on issue #405: core: avoid referencing application classes in bean build items and loading them in core build processors
URL: https://github.com/apache/camel-quarkus/pull/405#issuecomment-553292831
 
 
   > +1 for the goal, I also thought of doing it. Passing a class proxy instead of the class did not work for me on this place: https://github.com/apache/camel-quarkus/pull/402/files#diff-ec6205752018e84a80fcd9eaa92af189R320 so it probably won't work for you here: https://github.com/apache/camel-quarkus/pull/405/files#diff-ec6205752018e84a80fcd9eaa92af189R191 It might well be a bug in Quarkus.
   
   It should be fine now as the way it is used matches the pattern for which the class proxy is needed. In your code I suspect the problem was the fact that the proxy was owned by a build item and maybe triggering a bug (for which you may submit an issue to quarkus).
   
   The failure on CI is caused by the validator extension, don't know why.
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services