Hi Thomas thanks for the support. your svn commands below work to some degree!
bash$ jsvn info http://github.com/apache/maven-3/trunk 0: /DKA3/java_60/bin/java 1: -Dsun.io.useCanonCaches=false 2: -Djava.util.logging.config.file=/DKA3/stadelma/svnkit-1.3.5.7406/logging.properties 3: -cp 4: /DKA3/stadelma/svnkit-1.3.5.7406/svnkit.jar:/DKA3/stadelma/svnkit-1.3.5.7406/svnkit-cli.jar:/DKA3/stadelma/svnkit-1.3.5.7406/tril ead.jar:/DKA3/stadelma/svnkit-1.3.5.7406/jna.jar:/DKA3/stadelma/svnkit-1.3.5.7406/sqljet.1.0.4.jar:/DKA3/stadelma/svnkit-1.3.5.7406/ antlr-runtime-3.1.3.jar 5: org.tmatesoft.svn.cli.svn.SVN 6: info 7: http://github.com/apache/maven-3/trunk svn: Repository moved permanently to '/apache/maven-3/trunk'; please relocate svn: OPTIONS request failed on '/apache/maven-3/trunk' so this fails with http:// bash$ jsvn info https//github.com/apache/maven-3/trunk 0: /DKA3/java_60/bin/java 1: -Dsun.io.useCanonCaches=false 2: -Djava.util.logging.config.file=/DKA3/stadelma/svnkit-1.3.5.7406/logging.properties 3: -cp 4: /DKA3/stadelma/svnkit-1.3.5.7406/svnkit.jar:/DKA3/stadelma/svnkit-1.3.5.7406/svnkit-cli.jar:/DKA3/stadelma/svnkit-1.3.5.7406/tril ead.jar:/DKA3/stadelma/svnkit-1.3.5.7406/jna.jar:/DKA3/stadelma/svnkit-1.3.5.7406/sqljet.1.0.4.jar:/DKA3/stadelma/svnkit-1.3.5.7406/ antlr-runtime-3.1.3.jar 5: org.tmatesoft.svn.cli.svn.SVN 6: info 7: https://github.com/apache/maven-3/trunk Path: trunk URL: https://github.com/apache/maven-3/trunk Repository Root: https://github.com/apache/maven-3 Repository UUID: 5bc8a53d-41ec-bbf6-b094-ce57b7db7bff Revision: 9404 Node Kind: directory Last Changed Author: no.author Last Changed Rev: 9312 Last Changed Date: 2003-09-01 18:05:50 +0200 (Mon, 01 Sep 2003) so this works with https:// bash$ jsvn co https://github.com/apache/maven-3/trunk 0: /DKA3/java_60/bin/java 1: -Dsun.io.useCanonCaches=false 2: -Djava.util.logging.config.file=/DKA3/stadelma/svnkit-1.3.5.7406/logging.properties 3: -cp 4: /DKA3/stadelma/svnkit-1.3.5.7406/svnkit.jar:/DKA3/stadelma/svnkit-1.3.5.7406/svnkit-cli.jar:/DKA3/stadelma/svnkit-1.3.5.7406/tril ead.jar:/DKA3/stadelma/svnkit-1.3.5.7406/jna.jar:/DKA3/stadelma/svnkit-1.3.5.7406/sqljet.1.0.4.jar:/DKA3/stadelma/svnkit-1.3.5.7406/ antlr-runtime-3.1.3.jar 5: org.tmatesoft.svn.cli.svn.SVN 6: co 7: https://github.com/apache/maven-3/trunk A trunk/.gitattributes A trunk/.gitignore A trunk/README.bootstrap.txt A trunk/README.md A trunk/README.txt ... ... after 10 minutes of downloading, at ... ... A trunk/maven-core/src/site/apt/scripting-support/marmalade-support.apt A trunk/maven-core/src/site/resources A trunk/maven-core/src/site/resources/design A trunk/maven-core/src/site/resources/design/2.1-lifecycle-refactor-class-diagram.png svn: SSL peer shut down incorrectly svn: REPORT request failed on '/apache/maven-3/!svn/vcc/default' bash$ so this fails with https - but succeeded yesterday for an jsvn up with http, through our firewall. It started to work very nicely on openvms using "jsvn" (as we have no svn (c/c++ compiled version on OpenVMS we use jsvn)). Migrating also means to me bash$ rm -rf trunk/ deleting all old sources and only then does bash$ jsvn co https://github.com/apache-maven-3/trunk work. and BTW: it does only work for the https but not for the http protocol. Is this by intention of the administrator? So as long as I can jsvn co/up this git repo using jsvn from OpenVMS through the https protocol is all fine for me. BUT svn: SSL peer shutdown incorrectly kicks me out of the loop. Is it my JSVN-Client or the https://github.com Repository-Server which fails or the FW in between? what makes my jsvn fail after thousand of files are downloaded using jsvn co https://...? Josef -----Ursprüngliche Nachricht----- Von: Thomas Broyer [mailto:t.bro...@gmail.com] Gesendet: Montag, 7. Januar 2013 16:38 An: Maven Users List Betreff: Re: building from latest trunk On Mon, Jan 7, 2013 at 4:20 PM, Stadelmann Josef <josef.stadelm...@axa-winterthur.ch> wrote: > Does that mean that I can still use jsvn to update my maven trunk sources but > this time just from a different (git-hub)repository found under a different > url? AIUI, yes. > if yes: what is the correct svn checkout command to use? Try "svn co https://github.com/apache/maven-3/trunk"; and if it doesn't work, then try the 2-step "svn co --depth empty https://github.com/apache/maven-3"; then "svn up trunk" --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
