[kepler-dev] [Bug 5502] use https to svn check out modules
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Mon Nov 28 11:11:43 PST 2011
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5502
d.hogan at ge.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |d.hogan at ge.com
--- Comment #1 from d.hogan at ge.com 2011-11-28 11:11:43 PST ---
This would make it easier to track development behind a corporate firewall.
Attached is a patch that uses https for the standard modules. For http
proxies, you can add svn configuration for kepler in either
~/.subversion/servers or %APPDATA%/Subversion/servers
### svn config begin
[groups]
kepler = code.kepler-project.org, source.eecs.berkeley.edu
[kepler]
# http-proxy-exceptions = ... # as needed
http-proxy-host = your-proxy-host
http-proxy-port = 80
# The next two may be optional depending on your proxy configuration.
# Some allow https traffic without authentication
http-proxy-username = foo
http-proxy-password = bar
### svn config end
Index: src/org/kepler/build/project/RepositoryLocations.java
===================================================================
--- src/org/kepler/build/project/RepositoryLocations.java (revision
29007)
+++ src/org/kepler/build/project/RepositoryLocations.java (working copy)
@@ -41,7 +41,7 @@
public class RepositoryLocations
{
//Repository Locations
- public static String REPO = "http://code.kepler-project.org/code/kepler";
+ public static String REPO = "https://code.kepler-project.org/code/kepler";
public static String BRANCHES = REPO + "/releases/release-branches";
public static String RELEASED = REPO + "/releases/released";
public static String TEST_RELEASES = REPO + "/releases/test-releases";
If you use the above configuration and run "ant -f kepler-tasks.xml" from the
build-area directory to rebuild kepler-tasks.jar, it should checkout everything
over https.
--
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
More information about the Kepler-dev
mailing list