Hi,
We are facing the same issue
@jmrecheithink @rchilli @itohirin @julianprius @pavilandoangelo @ankit11088 The hosting team informed that they have reconfigured our maven repository. Now one request is allowed every 2 seconds. Could you please check whether the problem still persist on your side?
No, still not working as expected
On request from repository for compilation is getting passed then for other getting failed
Any update on the concern?
Still not working for me,
Could not resolve dependencies for project org:war:1.0.13: The following artifacts could not be resolved: com.aspose:aspose-words:jar:jdk17:24.5 (absent), com.aspose:aspose-words:jar:javadoc:24.5 (absent), com.aspose:aspose-words:jar:shaping-harfbuzz-plugin:24.5 (absent): Could not transfer artifact com.aspose:aspose-words:jar:jdk17:24.5 from/to AsposeJavaAPI (https://repository.aspose.com/repo/): status code: 403, reason phrase: Forbidden (403)
@itohirin Thank you for additional information. We increased the limit to two requests per second. Could you please recheck whether the problem still persists for you.
Hi @alexey.noskov , thanks for the reply i want to confirm for the version 24.5, for the repository should we use :
https://repository.aspose.com/repo/
or
https://releases.aspose.com/java/repo/
it appear when we use the first one, we get absent dependencies which is error, but its working fine and able to download in gitlab if we use the second one, if you acces manual the first url, it will redirect into second url, but i dont know if it the same in server cloud. any explanation ? thanks
@itohirin You shoudl use the following reporirory:
<repository>
<id>AsposeJavaAPI</id>
<name>Aspose Java API</name>
<url>https://releases.aspose.com/java/repo/</url>
</repository>
Hi @alexey.noskov , we get another error when AWS Try to create war file, did i miss something ?
[ERROR] Failed to execute goal on project: Could not resolve dependencies for project org:war:1.0.13: Could not find artifact com.aspose:aspose-words:jar:jdk17:24.5 in (file:/codebuild/output/src1272038365/src/repo) → [Help 1]
we currently use this
<repository>
<id>AsposeJavaAPI</id>
<name>Aspose Java API</name>
<url>https://releases.aspose.com/java/repo/</url>
</repository>
<dependency>
<groupId>com.aspose</groupId>
<artifactId>aspose-words</artifactId>
<version>24.5</version>
<classifier>jdk17</classifier>
</dependency>
thanks.
try renaming you .m2 to something else and do a build
I figured the issue for my case.
we were pointing to repository.aspose.com while the working config is releases.aspose.com
now I am confused how it worked till last week
@pankajkundlia We have reconfigured our maven repository and switched to the https://releases.aspose.com/java/repo/
sometime ago.