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

   Related to https://issues.apache.org/jira/browse/CAMEL-23389
   
   
   
   # Description
   
   
   The Atlassian Maven repository URL 
https://packages.atlassian.com/maven-external/ used in 
components/camel-jira/pom.xml was [deprecated as of February 1,
     
2025](https://developer.atlassian.com/server/framework/atlassian-sdk/maven-package-mirrors/).
   
   As of now, the old deprecated repo url started to fail in Camel Quarkus CI 
job, which builds Camel from source. The build fails during dependency 
resolution of camel-jira with:
   
   ```
     Failed to execute goal on project camel-jira: Could not collect 
dependencies for project org.apache.camel:camel-jira:jar:4.21.0-SNAPSHOT
     The following artifacts could not be resolved: 
com.atlassian.sal:sal-api:pom:7.2.1 (absent): Could not transfer artifact 
com.atlassian.sal:sal-api:pom:7.2.1 from/to atlassian
     (https://packages.atlassian.com/maven-external/): status code: 403, reason 
phrase: Forbidden (403)
   ```
   
     The solution should be to updated from 
https://packages.atlassian.com/maven-external/ to 
https://packages.atlassian.com/artifactory/maven-atlassian-all (which is used 
in suggested mvn setting)
   
   (if the change does not help, we can change the url to 
https://maven.artifacts.atlassian.com/, which is the final
     destination all Atlassian repositorie where are URLs now redirect to)
   
   <!--
   - Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   -->
   
   # Target
   
   - [ ] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [ ] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   <!--
   # *Note*: trivial changes like, typos, minor documentation fixes and other 
small items do not require a JIRA issue. In this case your pull request should 
address just this issue, without pulling in other changes.
   -->
   
   # Apache Camel coding standards and style
   
   - [ ] I checked that each commit in the pull request has a meaningful 
subject line and body.
   
   <!--
   If you're unsure, you can format the pull request title like `[CAMEL-XXX] 
Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the 
appropriate JIRA issue.
   -->
   
   - [ ] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   <!--
   You can run the aforementioned command in your module so that the build 
auto-formats your code. This will also be verified as part of the checks and 
your PR may be rejected if if there are uncommited changes after running `mvn 
clean install -DskipTests`.
   
   You can learn more about the contribution guidelines at 
https://github.com/apache/camel/blob/main/CONTRIBUTING.md
   -->
   
   


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

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to