In pom, need https in reference to repo.spring.io

[Dryocopus]

While trying to install PHIS via opensilex-phis-docker, I got an error:

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:01 min
[INFO] Finished at: 2020-02-07T13:10:42+00:00
[INFO] Final Memory: 21M/51M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project opensilex: Could not resolve dependencies for project com.mycompany:opensilex:war:v0.1: Failed to collect dependencies at com.twmacinta:fast-md5:jar:2.7.1: Failed to read artifact descriptor for com.twmacinta:fast-md5:jar:2.7.1: Could not transfer artifact com.twmacinta:fast-md5:pom:2.7.1 from/to spring-milestones (http://repo.spring.io/libs-milestone/): Access denied to: http://repo.spring.io/libs-milestone/com/twmacinta/fast-md5/2.7.1/fast-md5-2.7.1.pom , ReasonPhrase:Forbidden. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
ERROR: Service 'phis-ws' failed to build: The command '/bin/sh -c cd /home/phis/phis-ws/phis2-ws && mvn clean install -Pprod' returned a non-zero code: 1

Apparently this is because since 2020-01-15 the maven repository requires access to https. This policy is now also adopted by the spring repository. However, the pom.xml for phis-ws still refers to it with http:

    <repositories>
        <!--REPO CRYPTAGE-->
        <repository>
            <id>spring-milestones</id>
            <url>http://repo.spring.io/libs-milestone/</url>
        </repository>
    </repositories>

This is difficult to work around with the Docker install, so can it be fixed?

[dhobern]

Is anyone actively supporting phis-ws? I just debugged the Docker install and was about to raise the same issue.

[dhobern]

I've issued a pull request for the change

[aussieEd]

I'm having real issues installing this... I've changed the url of the repositry to https but am now having additional issues with errors reporting "Not authorized". any suggestions would be much appreciated.

[Dryocopus]

Hi aussieEd,

I opened this issue about a year ago, and don't remember what I did to work around it. In the meantime we migrated to a development version of PHIS, referenced here as https://github.com/OpenSILEX/opensilex-dev. In the Dockerfiles we made for that, i don't see any references to mvn, so it's probably no longer relevant. But a colleague has taken over this part of the work, so I may be wrong.

Anyway, opensilex-dev has never been released as production version, and we don't have a production-install either. Instead, a completely new version of PHIS will be released in a few months. That will differ significantly from both the current production version of PHIS and opensilex-dev, so I don't think migrating to opensilex-dev makes much sense.

I think you should discuss with the PHIS-team what is best to do at this stage. It will depend on how urgent your need for PHIS is.

We will create a Docker install for that new version anyway and if we think it is generic enough we will probably release it for the entire community.

[aussieEd]

Hi Dryocopus,
Thank you for taking the time to respond. It's much appreciated. I've reached out to PHIS-team and hopefully I am able to initialise a response from them. I'd be very keen on the Docker install if you create one, and I'm sure many other would to.