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:
in regard to apache/maven/trunk and what does not work?
Josef
-Ursprüngliche Nachricht-
Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch]
Gesendet: Dienstag, 8. Januar 2013 10:45
An: Maven Users List
Betreff: AW: building from latest trunk
Hi Thomas
thanks
Very much thanks Thomas,
But when I use the git://... protocol I cannot pass our fire wall because I
think it is not forseen by git to pass credentials to a proxy server when the
git protocol is used. within my .gitconfig I have set a http.proxy as
http://c770817:mypasw...@proxyserver.com:8080
thank you very much Kristian
that explains many thing.
BTW: do you know if with git.exe the proxy credentials can be passed using the
git://... protocol.
This just a general question. So far from egit/jgit forum nothing to a simple
question.
Josef
-Ursprüngliche Nachricht-
Von:
This morning I finished updating my sources from the
https://github.com/apache/maven-3/trunk repository. version 9404 is checked out.
I have then rebuilt
bash$ mvn clean install
on OpenVMS with all success.
The files mvn and mvnDebug mentioned below where also not included in the
tar.gz
but
Thanks Steven,
I assumed that! BUT are you saying that $ svn up does no longer work ...
AND
For me there is to say I do not have a git for OpenVMS yet,
hence this circumstances will complicate my src update cycles,
unless someone knows about a OpenVMS port of GIT!
Are you further saying
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?
if yes: what is the correct svn checkout command to use?
Thanks
Josef
-Ursprüngliche Nachricht-
Von: Thomas Broyer
