You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "JiriOndrusek (via GitHub)" <gi...@apache.org> on 2024/03/25 09:43:19 UTC

[PR] Upgrade camel to 4.5.0 [camel-quarkus]

JiriOndrusek opened a new pull request, #5921:
URL: https://github.com/apache/camel-quarkus/pull/5921

   <!-- Uncomment and fill this section if your PR is not trivial
   [ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes.
   [ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #.
   [ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough.
   [ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close the named issue upon merging the pull request. Using them is typically a good idea.
   [ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request.
   [ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html
   -->


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


Re: [PR] Upgrade camel to 4.5.0 [camel-quarkus]

Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton commented on PR #5921:
URL: https://github.com/apache/camel-quarkus/pull/5921#issuecomment-2025815122

   > 4.5.0 artifacts seems to be public accessible, let's try anoher ci run.
   
   I think there's an issue with the Splunk container image. Something has changed to make the splunk-hec test start failing. It's also observed on the `main` branch.


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


Re: [PR] Upgrade camel to 4.5.0 [camel-quarkus]

Posted by "JiriOndrusek (via GitHub)" <gi...@apache.org>.
JiriOndrusek commented on PR #5921:
URL: https://github.com/apache/camel-quarkus/pull/5921#issuecomment-2022212272

   There are 2 failures in examples:
   
   - **observability** - will be fixed after merging this PR https://github.com/apache/camel-quarkus/issues/5851
   - **kamelet-chucknorris** - the error is caused  by not resolving `camel-yaml-dsl`. , which is present in staging [repository](https://repository.apache.org/content/repositories/orgapachecamel-1689/org/apache/camel/camel-yaml-dsl/4.5.0/). (Locally the example works), therefore I would say, that it is not a real issue. WDYT? @jamesnetherton  
   ```
   ArtifactResolutionException: The following artifacts could not be resolved: org.apache.camel:camel-yaml-dsl:jar:4.5.0 (present, but unavailable): org.apache.camel:camel-yaml-dsl:jar:4.5.0 was not found in https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced
   ```


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


Re: [PR] Upgrade camel to 4.5.0 [camel-quarkus]

Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton merged PR #5921:
URL: https://github.com/apache/camel-quarkus/pull/5921


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


Re: [PR] Upgrade camel to 4.5.0 [camel-quarkus]

Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton commented on PR #5921:
URL: https://github.com/apache/camel-quarkus/pull/5921#issuecomment-2022220170

   > it is not a real issue
   
   Yeah. I was thinking that it's probably just luck that most of the example projects compile anyway. Since they don't have the staging repo configured in their project pom.xml.


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


Re: [PR] Upgrade camel to 4.5.0 [camel-quarkus]

Posted by "aldettinger (via GitHub)" <gi...@apache.org>.
aldettinger commented on PR #5921:
URL: https://github.com/apache/camel-quarkus/pull/5921#issuecomment-2025693035

   4.5.0 artifacts seems to be public accessible, let's try anoher ci run.


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


Re: [PR] Upgrade camel to 4.5.0 [camel-quarkus]

Posted by "ppalaga (via GitHub)" <gi...@apache.org>.
ppalaga commented on PR #5921:
URL: https://github.com/apache/camel-quarkus/pull/5921#issuecomment-2027962781

   Rebased and added the upgrade to cq-maven-plugin


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


Re: [PR] Upgrade camel to 4.5.0 [camel-quarkus]

Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton commented on PR #5921:
URL: https://github.com/apache/camel-quarkus/pull/5921#issuecomment-2024845352

   I regenerated the qdrant commit as it contained some unwanted stuff.


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


Re: [PR] Upgrade camel to 4.5.0 [camel-quarkus]

Posted by "aldettinger (via GitHub)" <gi...@apache.org>.
aldettinger commented on PR #5921:
URL: https://github.com/apache/camel-quarkus/pull/5921#issuecomment-2026819596

   > > 4.5.0 artifacts seems to be public accessible, let's try anoher ci run.
   > 
   > I think there's an issue with the Splunk container image. Something has changed to make the splunk-hec test start failing. It's also observed on the `main` branch.
   
   And it's also observed on the 3.8.x, at least in pr #5933 


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