[GitHub] [camel-quarkus] ppalaga opened a new pull request #698: Camel master update

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga opened a new pull request #698: Camel master update

GitBox
ppalaga opened a new pull request #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698
 
 
   

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli commented on issue #698: Camel master update

GitBox
lburgazzoli commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-584761569
 
 
   @ppalaga there are some build failures

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #698: Camel master update

GitBox
In reply to this post by GitBox
ppalaga commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-585198791
 
 
   > @ppalaga there are some build failures
   
   Yeah, there is never enough fun with remote snapshots. The Java 12 job was perhaps unlucky enough to get a newer snapshot that added a method to AbstractCamelContext. Because otherwise Java 8 should have failed too. Once we use the same cache for java 8 11 and 12 this should not happen anymore.

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #698: Camel master update

GitBox
In reply to this post by GitBox
ppalaga commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-585295345
 
 
   ConfigurerResolver adapts to the newest changes in Camel

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga edited a comment on issue #698: Camel master update

GitBox
In reply to this post by GitBox
ppalaga edited a comment on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-585295345
 
 
   3b260bc adapts to the newest changes in Camel

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #698: Camel master update

GitBox
In reply to this post by GitBox
ppalaga commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-585409220
 
 
   Failed due to transfer problems again. Let's rebase on top of master once https://github.com/apache/camel-quarkus/pull/705 is merged and see if the transfer problems go away.

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] jamesnetherton commented on issue #698: Camel master update

GitBox
In reply to this post by GitBox
jamesnetherton commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-585765636
 
 
   @ppalaga #705 is merged. Can we rebase this one and try again?

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #698: Camel master update

GitBox
In reply to this post by GitBox
ppalaga commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-585841818
 
 
   One more fix in e974195

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #698: Camel master update

GitBox
In reply to this post by GitBox
ppalaga commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-585854700
 
 
   There is never enough fun with snapshots. The CI apparently uses a different snapshot than my machine. There is no way to figure out which one is used by the CI and there is no way to force the two machines to use the same snapshot. What do you guys do in situations like this?

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] jamesnetherton commented on issue #698: Camel master update

GitBox
In reply to this post by GitBox
jamesnetherton commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-585868541
 
 
   The error is reproducible by slurping down the latest SNAPSHOTs. E.g build with `-U`.
   
   But you're right, it is a bit tricky to manage when the target keeps on moving.
   

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli commented on issue #698: Camel master update

GitBox
In reply to this post by GitBox
lburgazzoli commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-585869308
 
 
   > But you're right, it is a bit tricky to manage when the target keeps on moving.
   
   it is the funny part

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #698: Camel master update

GitBox
In reply to this post by GitBox
ppalaga commented on issue #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698#issuecomment-586172612
 
 
   Updated what I wanted, let's wait for the next random error.

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] jamesnetherton merged pull request #698: Camel master update

GitBox
In reply to this post by GitBox
jamesnetherton merged pull request #698: Camel master update
URL: https://github.com/apache/camel-quarkus/pull/698
 
 
   

----------------------------------------------------------------
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:
[hidden email]


With regards,
Apache Git Services