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 2020/02/14 10:34:21 UTC

[GitHub] [camel-quarkus] ppalaga opened a new pull request #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo

ppalaga opened a new pull request #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo
URL: https://github.com/apache/camel-quarkus/pull/720
 
 
   

----------------------------------------------------------------
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

[GitHub] [camel-quarkus] lburgazzoli merged pull request #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo

Posted by GitBox <gi...@apache.org>.
lburgazzoli merged pull request #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo
URL: https://github.com/apache/camel-quarkus/pull/720
 
 
   

----------------------------------------------------------------
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

[GitHub] [camel-quarkus] ppalaga commented on issue #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo

Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo
URL: https://github.com/apache/camel-quarkus/pull/720#issuecomment-586229451
 
 
   OK, I see that the props for the docker build have changed.

----------------------------------------------------------------
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

[GitHub] [camel-quarkus] ppalaga commented on issue #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo

Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo
URL: https://github.com/apache/camel-quarkus/pull/720#issuecomment-586232359
 
 
   ce43991 is using
   ```
                   <quarkus.native.container-build>true</quarkus.native.container-build>
                   <quarkus.native.container-runtime>docker</quarkus.native.container-runtime>
   ```
   
   instead of the old ones
   
   ```
                   <native-image.docker-build>true</native-image.docker-build>
                   <native-image.container-runtime>docker</native-image.container-runtime>
   ```

----------------------------------------------------------------
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

[GitHub] [camel-quarkus] ppalaga commented on issue #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo

Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #720: Fix #598 Use quarkus.package.type=native instead of the native-image mojo
URL: https://github.com/apache/camel-quarkus/pull/720#issuecomment-586380234
 
 
   f833a32 :
   
   * Rebased
   * Reverted the Jira itest, because it still does not work without the custom options. I hope @ffang will solve that in his upcoming PR. 
   * There was also a failure in the base64 itest due to missing camel-quarkus-base64.jar which I find unexplicable because it should have been provided by the `build` job. Maybe the Github actions cache is buggy?

----------------------------------------------------------------
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