[jira] [Assigned] (MESOS-10091) CI builds on ubuntu 14.04 fail to create Java bindings

["Benjamin Bannier (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bannier reassigned MESOS-10091:
----------------------------------------

    Assignee: Benjamin Bannier

> CI builds on ubuntu 14.04 fail to create Java bindings
> ------------------------------------------------------
>
>                 Key: MESOS-10091
>                 URL: https://issues.apache.org/jira/browse/MESOS-10091
>             Project: Mesos
>          Issue Type: Bug
>          Components: java api, reviewbot
>            Reporter: Benjamin Bannier
>            Assignee: Benjamin Bannier
>            Priority: Major
>
> Builds with Java bindings enabled fail on ubuntu-14.04 (this e.g., includes reviewbot builds) with the following error
> {noformat}
> 22:28:09 Building mesos-1.10.0.jar ...
> 22:28:09 /bin/sed -i.bak 's/mesos\.mesos_pb2/mesos_pb2/' python/interface/src/mesos/v1/interface/scheduler_pb2.py && rm python/interface/src/mesos/v1/interface/scheduler_pb2.py.bak
> 22:28:15 [ERROR] The build could not read 1 project -> [Help 1]
> 22:28:15 [ERROR]   
> 22:28:15 [ERROR]   The project org.apache.mesos:mesos:1.10.0 (/home/ubuntu/workspace/mesos/Mesos_CI-build/FLAG/SSL/label/mesos-ec2-ubuntu-14.04/mesos/build/src/java/mesos.pom) has 1 error
> 22:28:15 [ERROR]     Non-resolvable parent POM: Could not transfer artifact org.apache:apache:pom:11 from/to central (http://repo.maven.apache.org/maven2): Failed to transfer file: http://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom. Return code is: 501 , ReasonPhrase:HTTPS Required. and 'parent.relativePath' points at wrong local POM @ line 18, column 11 -> [Help 2]
> 22:28:15 [ERROR] 
> 22:28:15 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> 22:28:15 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 22:28:15 [ERROR] 
> 22:28:15 [ERROR] For more information about the errors and possible solutions, please read the following articles:
> 22:28:15 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> 22:28:15 [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> 22:28:15 make[1]: *** [java/target/mesos-1.10.0.jar] Error 1
> 22:28:15 make[1]: Leaving directory `/home/ubuntu/workspace/mesos/Mesos_CI-build/FLAG/SSL/label/mesos-ec2-ubuntu-14.04/mesos/build/src'
> 22:28:15 make: *** [all-recursive] Error 1
> {noformat}
> The error seems to be due to the maven version we use in ubuntu-14.04 CI images not using HTTPS by default [which seems required since 2020-01-15|https://support.sonatype.com/hc/en-us/articles/360041287334]
> {quote}
> Question
> As of January 15, 2020 I am receiving the following responses upon making requests to The Central Repository:
> Requests to http://repo1.maven.org/maven2/ return a 501 HTTPS Required status and a body:
> 501 HTTPS Required. 
> Use https://repo1.maven.org/maven2/
> More information at https://links.sonatype.com/central/501-https-required
> Requests to http://repo.maven.apache.org/maven2/ return a 501 HTTPS Required status and a body:
> 501 HTTPS Required. 
> Use https://repo.maven.apache.org/maven2/
> More information at https://links.sonatype.com/central/501-https-required
> How do I satisfy this requirement so that I can regain access to Central?
> Answer
> Effective January 15, 2020, The Central Repository no longer supports insecure communication over plain HTTP and requires that all requests to the repository are encrypted over HTTPS.
> If you're receiving this error, then you need to replace all URL references to Maven Central with their canonical HTTPS counterparts:
> Replace http://repo1.maven.org/maven2/ with https://repo1.maven.org/maven2/
> Replace http://repo.maven.apache.org/maven2/ with https://repo.maven.apache.org/maven2/
> If for any reason your environment cannot support HTTPS, you have the option of using our dedicated insecure endpoint at http://insecure.repo1.maven.org/maven2/
> For further context around the move to HTTPS, please see https://blog.sonatype.com/central-repository-moving-to-https.
> {quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)