Fixed. The following error was occurring:

     [exec] C:\openjump-nightly-build>svn co
https://jump-pilot.svn.sourceforge.net/svnroot/jump-pilot/core/trunk
--non-interactive C:\openjump-nightly-build\openjump
     [exec] svn: PROPFIND request failed on '/svnroot/jump-pilot/core/trunk'
     [exec] svn: PROPFIND of '/svnroot/jump-pilot/core/trunk': Server
certificate verification failed: issuer is not trusted
(https://jump-pilot.svn.sourceforge.net)
 
I ran the command line without the "--non-interactive" switch, accepted the
certificate, and the build now runs.

Jon




-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Giuseppe Aruta
Sent: Friday, October 26, 2007 10:48 PM
To: List for discussion of JPP development and use.
Subject: [JPP-Devel] OpenJUMP Nightly Build is still off

:-) OpenJUMP Nightly Build still shows only source folder

Peppe




      ___________________________________
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail:
http://it.docs.yahoo.com/nowyoucan.html


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to