Skip to content

build.sh fails because Maven now requires HTTPS to be used instead of HTTP #315

@alexhenrie

Description

@alexhenrie

./build.sh fails with the following error on my computer:

[ERROR] Failed to execute goal on project OWLTools-Core: Could not resolve dependencies for project org.bbop:OWLTools-Core:jar:0.3.0-SNAPSHOT: Failed to collect dependencies at org.bbop:oboformat-tools:jar:0.7.3: Failed to read artifact descriptor for org.bbop:oboformat-tools:jar:0.7.3: Could not transfer artifact org.bbop:oboformat-tools:pom:0.7.3 from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [BerkeleyBOP (http://code.berkeleybop.org/maven/repository/, default, releases+snapshots), BerkeleyBOPSnapshot (http://code.berkeleybop.org/maven/snapshot-repository/, default, releases+snapshots)] -> [Help 1]

This is because Maven 3.8.1, released in April, blocks HTTP downloads by default to prevent man-in-the-middle attacks. Could you please move http://code.berkeleybop.org/maven/repository/ to https://code.berkeleybop.org/maven/repository/ (or another HTTPS location) and update the URLs in OWLTools-Parent/pom.xml?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions