Thanks Steve for taking care of this. Once this issue is fixed, I will create a release plan for Trafodion R2.4 release Can the previous release managers send the pointers to enable me to jump start this process.
Regards Selva -----Original Message----- From: Steve Varnau <steve.var...@esgyn.com> Sent: Thursday, January 23, 2020 10:14 AM To: dev@trafodion.apache.org Subject: RE: Maven central change cause build failure External I have been looking at this a bit. I have seen issues in both JDBC build and TRX builds. I want to prove I can do complete build starting from empty maven repo (~/.m2/repository), since having dependencies cached there can mask problems. I can get past some of the issues by using newest (3.6.3) version of maven, instead of the 3.0.5 version. Then java 1.7 has some issues that I can get passed by setting TLSv1.2 option (JAVA_TOOL_OPTIONS="-Dhttps.protocols=TLSv1.2,TLSv1.1,TLSv1"). But I still run into some handshake_failure with repository.cloudera.com, when building the CDH-compatible TRX jar. Alternatively, I found that I was able to get a complete successful build if I used the new maven and I set JAVA_HOME to a 1.8 JDK (except DCS docs for some reason). Is there any concerns with moving up to requiring JDK 1.8 for trafodion? I have not yet regression tested this combination. Meanwhile, I will also try upgrading to the latest 1.7 JDK to see if that helps. I have logged Jira TRAFODION-3333 for this. -Steve From: Steve Varnau Sent: Thursday, January 16, 2020 10:00 AM To: dev@trafodion.apache.org Subject: Maven central change cause build failure Hi folks, Looks like a change at maven central to not allow http access has caused the daily trafodion build to fail: [INFO] Building Trafodion JDBC Type4 Driver 2.4.0 ##(JDBCT4) [INFO] BUILD FAILURE ##(JDBCT4) [ERROR] Plugin org.codehaus.mojo:properties-maven-plugin:1.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:properties-maven-plugin:jar:1.0.0: Could not transfer artifact org.codehaus.mojo:properties-maven-plugin:pom:1.0.0 from/to central (http://repo.maven.apache.org/maven2): Failed to transfer file: http://repo.maven.apache.org/maven2/org/codehaus/mojo/properties-maven-plugin/1.0.0/properties-maven-plugin-1.0.0.pom. Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1] ##(JDBCT4) [ERROR] ##(JDBCT4) Someone have time to look into fixing this up? I think builds will all fail until this gets fixed. -Steve
