Maven Repo is not holding latest artifacts

Aspose.PDF Product Family
1

Hi there,

we just saw that the maven repo is not holding the latest artifacts. E.g.:

only shows the versions until 18.1

11.1.0/ 30-Dec-2015 17:16 - 11.2.0/ 08-Feb-2016 10:16 - 11.3.0/ 07-Mar-2016 09:26 - 11.4.0/ 08-Apr-2016 16:25 - 11.5.0/ 10-May-2016 07:26 - 11.6.0/ 10-Jun-2016 12:39 - 11.7.0/ 12-Jul-2016 14:19 - 11.8.0/ 11-Aug-2016 14:48 - 11.9.0/ 20-Sep-2016 09:25 - 12.0.0/ 10-Oct-2016 08:44 - 16.10.0/ 26-Oct-2016 13:16 - 16.11.0/ 29-Nov-2016 11:43 - 16.12.0/ 27-Dec-2016 08:35 - 17.1.0/ 26-Jan-2017 10:02 - 17.10/ 01-Nov-2017 15:37 - 17.11/ 30-Nov-2017 08:13 - 17.12/ 31-Dec-2017 17:04 - 17.2.0/ 23-Feb-2017 10:32 - 17.3.0/ 06-Apr-2017 13:53 - 17.4/ 28-Apr-2017 07:22 - 17.5/ 07-Jun-2017 08:12 - 17.6/ 29-Jun-2017 05:23 - 17.7/ 20-Jul-2017 12:22 - 17.8/ 31-Aug-2017 09:31 - 17.9/ 02-Oct-2017 08:07 - 18.1/ 06-Feb-2018 09:05 -

Kind regards
Patrick

2

Worse than that, the only directories left are those under com/aspose. My build breaks because Aspose’s pom tries to access the com/google/code/typica package and gets a “410 Gone” (so I browsed, and found that to be true).

Raises the question why Maven tries to access that site and not our internal central Artifactory installation as it is configured to do

3

Same situation from our side. We are even missing an internal proxy which is now in the pipeline for our DevOps teams.

4

@Gwaptiva, @pkvogt

Please use following maven repository to get the desired version of Aspose.PDF.
https://repository.aspose.com/repo/com/aspose/aspose-pdf/

6

Thanks @tahir.manzoor - I guess this will resolve at least our issue.

Regards
Patrick

7

@Gwaptiva @pkvogt

Here is the latest configuration to access our repository.

<repositories>
<repository>
<id>AsposeJavaRepository</id>
<name>Aspose Java Repository</name>
<url>https://repository.aspose.com/repo/</url>
</repository>
</repositories>

Feel free to reach us for any issue related to it. Thanks.

8

Hi @farooq.sheikh, using this new repository works for my local environment, but my builds ran on Github Actions are failing on a 403 error. Can you please whitelist Github Actions?

This is my error message:

Could not resolve com.aspose:aspose-pdf:21.12.

Could not get resource ‘https://repository.aspose.com/repo/com/aspose/aspose-pdf/21.12/aspose-pdf-21.12.pom’.

Could not GET ‘https://repository.aspose.com/repo/com/aspose/aspose-pdf/21.12/aspose-pdf-21.12.pom’. Received status code 403 from server: Forbidden

9

@draftwise

his new repository works for my local environment, but my builds ran on Github Actions are failing on a 403 error. Can you please whitelist Github Actions?

It looks like Github Actions is still using cache DNS entry of repository.apose.com. That’s why it is failing but working with local. Our repository DNS record has been updated in last weekend and point to new server. Please make sure to use latest DNS record in your Github Actions to get it work.

Feel free to reach us for any question related to it. Thanks.

10

@farooq.sheikh I opened a ticket with GH actions with a link to your explanation. Interestingly, when I rerun the GH action, it succeeded 1 time, but on the next ~5 tries, it consistently fails on the 403. Is that consistent with your theory, or is it possible there’s something on the Aspose repository side that this may indicate a misconfiguration with?

11

@draftwise

We are working over this issue and will let you know once it is resolved. Thanks for your patience and understanding.

12

Thank you @tahir.manzoor and @farooq.sheikh. I received an update from Github support last night which says this:

GitHub Actions does not cache DNS. The 403 Forbidden response code indicates that the receiving server *is* being connected to, yet authentication is being checked and rejected. In particular, given one of the workflow runs succeeded yet another is still failing suggests the failure is external to GitHub Actions.

13

@draftwise

Please try now. Our hosting team has updated their FW configurations. GH actions is working fine at my end. Kindly verify now.

Feel free to reach us for any issue related to it. Thanks.

14

Thank you @farooq.sheikh!