Note that I poked in the ant build file a bit to see what is going on when the initial https is happening. I then found that if I do the initial svn checkout of the enhanced trunk via
Svn co https://svn.apache.org/repos/asf/harmony/enhanced/trunk Instead of what is suggested on the web page: Svn co http://svn.apache.org/repos/asf/harmony/enhanced/trunk I am given the opportunity to accept the certificate permanently at that point in time allowing it to proceed. This doesn't necessarily answer all the questions below but does allow me to make some forward progress. Thx, Chris -----Original Message----- From: Elford, Chris L [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 18, 2007 6:25 PM To: [email protected] Subject: Federated build question Hi all, I've not built Harmony in a while (I've been using snapshot builds) but needed to build myself for a change. I am using Harmony M3 to try to launch a federated build on a new system (linux -- Ubuntu)... Ant shows the following when I try to build the first time: [exec] Fetching external item into 'modules/concurrent/standard' [exec] Error validating server certificate for 'https://svn.apache.org:443': [exec] - The certificate is not issued by a trusted authority. Use the [exec] fingerprint to validate the certificate manually! [exec] Certificate information: [exec] - Hostname: svn.apache.org [exec] - Valid: from Fri, 26 Jan 2007 14:18:55 GMT until Mon, 26 Jan 2009 14:18:55 GMT [exec] - Issuer: http://www.starfieldtech.com/repository, Starfield Technologies, Inc., Scottsdale, Arizona, US [exec] - Fingerprint: a7:a5:3f:1a:ae:bb:98:b2:f3:ec:91:1b:63:29:2d:e8:58:b6:53:28 [exec] (R)eject, accept (t)emporarily or accept (p)ermanently? svn: PROPFIND request failed on '/repos/asf/harmony/standard/classlib/trunk/modules/concurrent' [exec] svn: PROPFIND of '/repos/asf/harmony/standard/classlib/trunk/modules/concurrent': Server certificate verification failed: issuer is not trusted (https://svn.apache.org) If I repeat the ant command (I have to set ANT_OPTS to indicate a proxy for -Dauto.fetch=true to work), Instead of printing this error again, it gets further and then fails with: -compile: [mkdir] Created dir: /usr/local/src/harmony/trunk/working_classlib/build/classes BUILD FAILED /usr/local/src/harmony/trunk/build.xml:323: The following error occurred while executing this line: /usr/local/src/harmony/trunk/working_classlib/build.xml:113: The following error occurred while executing this line: /usr/local/src/harmony/trunk/working_classlib/make/build-java.xml:120: srcdir "/usr/local/src/harmony/trunk/working_classlib/modules/concurrent/standa rd/src/main/java" does not exist! Is there a reason that the federated build needs to download modules/concurrent/standard via https instead of plain http? What is the easy way to accept the certificate on the first build so that the build will proceed? Is there a reason that it does not realize that there was a failure the first time around? Thanks, Chris Elford Intel SSG/Enterprise Solutions Software Division
