You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Stadelmann Josef <jo...@axa-winterthur.ch> on 2013/01/07 14:47:03 UTC
building from latest trunk
Hi,
I did
openVMS>
bash$ svn co trunk
bash$ mvn clean install
bash$
all the build steps indicates SUCCESS; lets do a cd and inspect
bash$ cd /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT
bash$ ls -l
total 10205
-rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12
apache-maven-3.1-SNAPSHOT-bin.tar.gz
-rwxr-x--- 1 STADELMA 129 5234859 Jan 7 12:12
apache-maven-3.1-SNAPSHOT-bin.zip
-rwxr-x--- 1 STADELMA 129 1113 Jan 7 12:12
apache-maven-3.1-SNAPSHOT-site.xml
-rwxr-x--- 1 STADELMA 129 5569 Jan 7 12:12
apache-maven-3.1-SNAPSHOT.pom
-rwxr-x--- 1 STADELMA 129 316 Jan 7 12:12
maven-metadata-local.xml
openVMS> copy apache-maven-3.1-SNAPSHOT-bin.tar.gz sys$login:
apache-maven-3.1-SNAPSHOT-bin.tar.gz
openVMS> set def sys$login
openVMS>bash
bash$ gnutar -vzxf apache-maven-3.1-SNAPSHOT-bin.tar.gz
and I get the just built maven-3.1-snapshot installed
BUT
Now I am facing one problem I've never seen before.
***************************************************
bash$ cd $HOME/apache-maven-3.1-SNAPSHOT
bash$ ls -l
total 13
-rwxr-x--- 1 STADELMA 129 230 Jan 7 12:12 m2.conf
-rwxr-x--- 1 STADELMA 129 6152 Jan 7 12:12 mvn.bat
-rwxr-x--- 1 STADELMA 129 6306 Jan 7 12:12 mvnDebug.bat
I am facing the following problem!
why was mvn and mvnDebug (the shell files) not packaged into my target
*tar.gz file?
lets look at the sources
openVMS> set def
DKA3:[SW-PROJEKTE.asf.maven.maven-3.trunk.apache-maven.src.bin]
bash$ ls -l
total 31
drwxr-x--- 1 STADELMA 129 512 Oct 30 16:27 _svn
-rwxr-x--- 1 STADELMA 129 222 Oct 30 16:27 m2.conf
-rwxr-x--- 1 STADELMA 129 5807 Jan 7 11:28 mvn
-rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvn.bat
-rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvnDebug
-rwxr-x--- 1 STADELMA 129 6106 Jan 7 11:28 mvnDebug.bat
-rwxr-x--- 1 STADELMA 129 6115 Jan 7 11:28 mvnyjp
bash$
all there, just not packaged with my tar.gz and maybe .zip file
any hints welcome
Josef
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: building from latest trunk
Posted by Olivier Lamy <ol...@apache.org>.
2013/1/7 Stadelmann Josef <jo...@axa-winterthur.ch>:
> 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 that maven trunk sources are no longer making it into the svn repo?
yes
not all sources currently see ETA here
https://cwiki.apache.org/MAVEN/git-migration.html
>
> in this case - reading at
> http://maven.apache.org/guides/development/guide-building-m2.html
> indicates that as alternative one can still use svn co ....
> but this has no value if this repo is not updated by developers.
>
this "alternative" is wrong, I have just fixed that.
>
> For my problem as work around ...
> I just copied the 2 missing files mvn and mvnDebug from the kit into m2_home/bin
> and then did
> OpenVMS> bash
> bash$ mvn -version
> Apache Maven 3.1-SNAPSHOT (rNON-CANONICAL_2013-01-07_12-07_STADELMA; 2013-01-07 12:07:04+0100)
> Maven home: /dka3/stadelma/apache-maven-3.1
> Java version: 1.6.0, vendor: Hewlett-Packard Company
> Java home: /DKA3/java_60/JRE
> Default locale: en, platform encoding: ISO8859-1
> OS name: "openvms", version: "v8.4", arch: "ia64", family: "openvms"
> bash$
>
> But I don't know why the maven build did not package this two files into my tar.gz or zip file.
>
> Josef
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Gesendet: Montag, 7. Januar 2013 14:56
> An: Maven Users List
> Betreff: Re: building from latest trunk
>
> Not an answer for you but an FYI: Maven trunk has moved to git
>
>
> On 7 January 2013 13:47, Stadelmann Josef < josef.stadelmann@axa-winterthur.ch> wrote:
>
>> Hi,
>>
>> I did
>> openVMS>
>> bash$ svn co trunk
>> bash$ mvn clean install
>> bash$
>>
>> all the build steps indicates SUCCESS; lets do a cd and inspect
>>
>> bash$ cd
>> /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT
>> bash$ ls -l
>> total 10205
>> -rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12
>> apache-maven-3.1-SNAPSHOT-bin.tar.gz
>> -rwxr-x--- 1 STADELMA 129 5234859 Jan 7 12:12
>> apache-maven-3.1-SNAPSHOT-bin.zip
>> -rwxr-x--- 1 STADELMA 129 1113 Jan 7 12:12
>> apache-maven-3.1-SNAPSHOT-site.xml
>> -rwxr-x--- 1 STADELMA 129 5569 Jan 7 12:12
>> apache-maven-3.1-SNAPSHOT.pom
>> -rwxr-x--- 1 STADELMA 129 316 Jan 7 12:12
>> maven-metadata-local.xml
>>
>> openVMS> copy apache-maven-3.1-SNAPSHOT-bin.tar.gz sys$login:
>> apache-maven-3.1-SNAPSHOT-bin.tar.gz
>> openVMS> set def sys$login
>> openVMS>bash
>> bash$ gnutar -vzxf apache-maven-3.1-SNAPSHOT-bin.tar.gz
>>
>> and I get the just built maven-3.1-snapshot installed
>>
>> BUT
>> Now I am facing one problem I've never seen before.
>> ***************************************************
>>
>> bash$ cd $HOME/apache-maven-3.1-SNAPSHOT bash$ ls -l total 13
>> -rwxr-x--- 1 STADELMA 129 230 Jan 7 12:12 m2.conf
>> -rwxr-x--- 1 STADELMA 129 6152 Jan 7 12:12 mvn.bat
>> -rwxr-x--- 1 STADELMA 129 6306 Jan 7 12:12 mvnDebug.bat
>>
>> I am facing the following problem!
>> why was mvn and mvnDebug (the shell files) not packaged into my target
>> *tar.gz file?
>>
>> lets look at the sources
>>
>> openVMS> set def
>> DKA3:[SW-PROJEKTE.asf.maven.maven-3.trunk.apache-maven.src.bin]
>> bash$ ls -l
>> total 31
>> drwxr-x--- 1 STADELMA 129 512 Oct 30 16:27 _svn
>> -rwxr-x--- 1 STADELMA 129 222 Oct 30 16:27 m2.conf
>> -rwxr-x--- 1 STADELMA 129 5807 Jan 7 11:28 mvn
>> -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvn.bat
>> -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvnDebug
>> -rwxr-x--- 1 STADELMA 129 6106 Jan 7 11:28 mvnDebug.bat
>> -rwxr-x--- 1 STADELMA 129 6115 Jan 7 11:28 mvnyjp
>>
>> bash$
>>
>> all there, just not packaged with my tar.gz and maybe .zip file
>>
>> any hints welcome
>> Josef
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: building from latest trunk
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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: kristian.rosenvold@zenior.no [mailto:kristian.rosenvold@zenior.no] Im Auftrag von Kristian Rosenvold
Gesendet: Dienstag, 8. Januar 2013 12:34
An: Maven Users List
Betreff: Re: building from latest trunk
We are re-arranging the mirroring layout on github, and the current git repos on github seem to be in a state of flux. Hopefully this smoothens out "soon".
I would recommend using
https://git-wip-us.apache.org/repos/asf/maven.git until they shape up.
This is the authorative master repo as well !
Kristian
2013/1/8 Thomas Broyer <t....@gmail.com>:
> On Tue, Jan 8, 2013 at 12:16 PM, Stadelmann Josef
> <jo...@axa-winterthur.ch> wrote:
>> Thomas
>>
>> I take TortoiseGit on Windows Vista to clone from maven-3/trunk/ but it seams that none of the git supported protocols are supported there.
>
> No, the Git repo is at https://github.com/apache/maven-3.git
>
> But if you're using Git, then you can use the repo from Apache:
> git://git.apache.org/maven-3.git
>
> See http://git.apache.org/ (search for maven-3 on the page) and
> https://github.com/apache/maven-3 (clone URLs are given at the top of
> the page)
>
> --
> Thomas Broyer
> /tɔ.ma.bʁwa.je/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: building from latest trunk
Posted by Kristian Rosenvold <kr...@gmail.com>.
We are re-arranging the mirroring layout on github, and the current
git repos on github seem to be in a state of flux. Hopefully this
smoothens out "soon".
I would recommend using
https://git-wip-us.apache.org/repos/asf/maven.git until they shape up.
This is the authorative master repo as well !
Kristian
2013/1/8 Thomas Broyer <t....@gmail.com>:
> On Tue, Jan 8, 2013 at 12:16 PM, Stadelmann Josef
> <jo...@axa-winterthur.ch> wrote:
>> Thomas
>>
>> I take TortoiseGit on Windows Vista to clone from maven-3/trunk/ but it seams that none of the git supported protocols are supported there.
>
> No, the Git repo is at https://github.com/apache/maven-3.git
>
> But if you're using Git, then you can use the repo from Apache:
> git://git.apache.org/maven-3.git
>
> See http://git.apache.org/ (search for maven-3 on the page) and
> https://github.com/apache/maven-3 (clone URLs are given at the top of
> the page)
>
> --
> Thomas Broyer
> /tɔ.ma.bʁwa.je/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: building from latest trunk
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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:mypasword@proxyserver.com:8080 still missing the http.auth.preference=Basic attribute which stops our proxy server from negotiating but enforces it to start a basic authentication session with username and password. That works for http://... to many git-repo-server.
So
git://.. is not passing credentials to proxy server
http:/.. passing proxy credentials is not supported at your side of the pond
https://.. works but I was kicked out many times from ssl peer and have to jsvn co in junks, one directory after one directory of the trunk. This is very annoying.
Josef
-----Ursprüngliche Nachricht-----
Von: Thomas Broyer [mailto:t.broyer@gmail.com]
Gesendet: Dienstag, 8. Januar 2013 12:29
An: Maven Users List
Betreff: Re: building from latest trunk
On Tue, Jan 8, 2013 at 12:16 PM, Stadelmann Josef <jo...@axa-winterthur.ch> wrote:
> Thomas
>
> I take TortoiseGit on Windows Vista to clone from maven-3/trunk/ but it seams that none of the git supported protocols are supported there.
No, the Git repo is at https://github.com/apache/maven-3.git
But if you're using Git, then you can use the repo from Apache:
git://git.apache.org/maven-3.git
See http://git.apache.org/ (search for maven-3 on the page) and
https://github.com/apache/maven-3 (clone URLs are given at the top of the page)
--
Thomas Broyer
/tɔ.ma.bʁwa.je/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: building from latest trunk
Posted by Thomas Broyer <t....@gmail.com>.
On Tue, Jan 8, 2013 at 12:16 PM, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> Thomas
>
> I take TortoiseGit on Windows Vista to clone from maven-3/trunk/ but it seams that none of the git supported protocols are supported there.
No, the Git repo is at https://github.com/apache/maven-3.git
But if you're using Git, then you can use the repo from Apache:
git://git.apache.org/maven-3.git
See http://git.apache.org/ (search for maven-3 on the page) and
https://github.com/apache/maven-3 (clone URLs are given at the top of
the page)
--
Thomas Broyer
/tɔ.ma.bʁwa.je/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: building from latest trunk
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Thomas
I take TortoiseGit on Windows Vista to clone from maven-3/trunk/ but it seams that none of the git supported protocols are supported there.
Or do I something wrong, even when I have used TortoiseGit for clonig a few times very well.?
--- 1. attempt using https ---
git.exe clone --recursive --progress -v "git clone https://github.com/apache/maven-3/trunk" "E:\hub\maven-3\trunk"
Cloning into 'E:\hub\maven-3\trunk'...
fatal: I don't handle protocol 'git clone https'
git did not exit cleanly (exit code 128) (234 ms @ 08.01.2013 12:06:37)
--- 2. attempt using http ---
git.exe clone --progress -v "git clone http://github.com/apache/maven-3/trunk" "E:\hub\maven-3\trunk"
Cloning into 'E:\hub\maven-3\trunk'...
fatal: I don't handle protocol 'git clone http'
git did not exit cleanly (exit code 128) (1591 ms @ 08.01.2013 12:08:01)
--- 3. attempt using https ---
git.exe clone --progress -v "git clone git://github.com/apache/maven-3/trunk" "E:\hub\maven-3\trunk"
Cloning into 'E:\hub\maven-3\trunk'...
fatal: I don't handle protocol 'git clone git'
git did not exit cleanly (exit code 128) (359 ms @ 08.01.2013 12:08:46)
over all using
bash$ jsvn --depth infinity https://github.com/apache/maven-3/trunk/apache-maven apache-maven
on a one by one basis succeeded, but checking out the whole maven-3/trunk/ at once always fails.
Doing the same using jsvn to a axis2 svn repository for the whole axis2 trunk succeeded without any problem. Difference: axis2 jsvn uses http while maven-3 used https. Can that make a difference or is the github.com server shaky or do I run into a limit setup server side or client side at the fire wall?
(see my previous e-mail for that)
Please:
Would potentially somebody explain what works up-to-day with this github.com repository in regard to apache/maven/trunk and what does not work?
Josef
-----Ursprüngliche Nachricht-----
Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
Gesendet: Dienstag, 8. Januar 2013 10:45
An: Maven Users List
Betreff: AW: building from latest trunk
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.broyer@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 <jo...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
-----------------------
ssi,-i e-ssi@v.aer
rdtn mn,-i e-lmeac.g
AW: building from latest trunk
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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.broyer@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 <jo...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: building from latest trunk
Posted by Thomas Broyer <t....@gmail.com>.
On Mon, Jan 7, 2013 at 4:20 PM, Stadelmann Josef
<jo...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: building from latest trunk
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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 [mailto:t.broyer@gmail.com]
Gesendet: Montag, 7. Januar 2013 15:52
An: Maven Users List
Betreff: Re: building from latest trunk
On Mon, Jan 7, 2013 at 3:32 PM, Stephen Connolly <st...@gmail.com> wrote:
> Those docs are in the process of being rewitten... they are sadly not
> what they should be. AFAIK you will need GIT to get the latest core
> distribution...
>
> If you dont need latest, you can get the release tarballs...
>
> And there is always the ability to get a .zip of the core source
> though some magic via github
GitHub also exposes every repo as SVN:
https://github.com/blog/1178-collaborating-on-github-with-subversion
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: building from latest trunk
Posted by Thomas Broyer <t....@gmail.com>.
On Mon, Jan 7, 2013 at 3:32 PM, Stephen Connolly
<st...@gmail.com> wrote:
> Those docs are in the process of being rewitten... they are sadly not what
> they should be. AFAIK you will need GIT to get the latest core
> distribution...
>
> If you dont need latest, you can get the release tarballs...
>
> And there is always the ability to get a .zip of the core source though
> some magic via github
GitHub also exposes every repo as SVN:
https://github.com/blog/1178-collaborating-on-github-with-subversion
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: building from latest trunk
Posted by Stephen Connolly <st...@gmail.com>.
Those docs are in the process of being rewitten... they are sadly not what
they should be. AFAIK you will need GIT to get the latest core
distribution...
If you dont need latest, you can get the release tarballs...
And there is always the ability to get a .zip of the core source though
some magic via github
On 7 January 2013 14:12, Stadelmann Josef <
josef.stadelmann@axa-winterthur.ch> wrote:
> 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 that maven trunk sources are no longer making it
> into the svn repo?
>
> in this case - reading at
> http://maven.apache.org/guides/development/guide-building-m2.html
> indicates that as alternative one can still use svn co ....
> but this has no value if this repo is not updated by developers.
>
>
> For my problem as work around ...
> I just copied the 2 missing files mvn and mvnDebug from the kit into
> m2_home/bin
> and then did
> OpenVMS> bash
> bash$ mvn -version
> Apache Maven 3.1-SNAPSHOT (rNON-CANONICAL_2013-01-07_12-07_STADELMA;
> 2013-01-07 12:07:04+0100)
> Maven home: /dka3/stadelma/apache-maven-3.1
> Java version: 1.6.0, vendor: Hewlett-Packard Company
> Java home: /DKA3/java_60/JRE
> Default locale: en, platform encoding: ISO8859-1
> OS name: "openvms", version: "v8.4", arch: "ia64", family: "openvms"
> bash$
>
> But I don't know why the maven build did not package this two files into
> my tar.gz or zip file.
>
> Josef
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Gesendet: Montag, 7. Januar 2013 14:56
> An: Maven Users List
> Betreff: Re: building from latest trunk
>
> Not an answer for you but an FYI: Maven trunk has moved to git
>
>
> On 7 January 2013 13:47, Stadelmann Josef <
> josef.stadelmann@axa-winterthur.ch> wrote:
>
> > Hi,
> >
> > I did
> > openVMS>
> > bash$ svn co trunk
> > bash$ mvn clean install
> > bash$
> >
> > all the build steps indicates SUCCESS; lets do a cd and inspect
> >
> > bash$ cd
> > /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT
> > bash$ ls -l
> > total 10205
> > -rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12
> > apache-maven-3.1-SNAPSHOT-bin.tar.gz
> > -rwxr-x--- 1 STADELMA 129 5234859 Jan 7 12:12
> > apache-maven-3.1-SNAPSHOT-bin.zip
> > -rwxr-x--- 1 STADELMA 129 1113 Jan 7 12:12
> > apache-maven-3.1-SNAPSHOT-site.xml
> > -rwxr-x--- 1 STADELMA 129 5569 Jan 7 12:12
> > apache-maven-3.1-SNAPSHOT.pom
> > -rwxr-x--- 1 STADELMA 129 316 Jan 7 12:12
> > maven-metadata-local.xml
> >
> > openVMS> copy apache-maven-3.1-SNAPSHOT-bin.tar.gz sys$login:
> > apache-maven-3.1-SNAPSHOT-bin.tar.gz
> > openVMS> set def sys$login
> > openVMS>bash
> > bash$ gnutar -vzxf apache-maven-3.1-SNAPSHOT-bin.tar.gz
> >
> > and I get the just built maven-3.1-snapshot installed
> >
> > BUT
> > Now I am facing one problem I've never seen before.
> > ***************************************************
> >
> > bash$ cd $HOME/apache-maven-3.1-SNAPSHOT bash$ ls -l total 13
> > -rwxr-x--- 1 STADELMA 129 230 Jan 7 12:12 m2.conf
> > -rwxr-x--- 1 STADELMA 129 6152 Jan 7 12:12 mvn.bat
> > -rwxr-x--- 1 STADELMA 129 6306 Jan 7 12:12 mvnDebug.bat
> >
> > I am facing the following problem!
> > why was mvn and mvnDebug (the shell files) not packaged into my target
> > *tar.gz file?
> >
> > lets look at the sources
> >
> > openVMS> set def
> > DKA3:[SW-PROJEKTE.asf.maven.maven-3.trunk.apache-maven.src.bin]
> > bash$ ls -l
> > total 31
> > drwxr-x--- 1 STADELMA 129 512 Oct 30 16:27 _svn
> > -rwxr-x--- 1 STADELMA 129 222 Oct 30 16:27 m2.conf
> > -rwxr-x--- 1 STADELMA 129 5807 Jan 7 11:28 mvn
> > -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvn.bat
> > -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvnDebug
> > -rwxr-x--- 1 STADELMA 129 6106 Jan 7 11:28 mvnDebug.bat
> > -rwxr-x--- 1 STADELMA 129 6115 Jan 7 11:28 mvnyjp
> >
> > bash$
> >
> > all there, just not packaged with my tar.gz and maybe .zip file
> >
> > any hints welcome
> > Josef
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
AW: building from latest trunk
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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 that maven trunk sources are no longer making it into the svn repo?
in this case - reading at
http://maven.apache.org/guides/development/guide-building-m2.html
indicates that as alternative one can still use svn co ....
but this has no value if this repo is not updated by developers.
For my problem as work around ...
I just copied the 2 missing files mvn and mvnDebug from the kit into m2_home/bin
and then did
OpenVMS> bash
bash$ mvn -version
Apache Maven 3.1-SNAPSHOT (rNON-CANONICAL_2013-01-07_12-07_STADELMA; 2013-01-07 12:07:04+0100)
Maven home: /dka3/stadelma/apache-maven-3.1
Java version: 1.6.0, vendor: Hewlett-Packard Company
Java home: /DKA3/java_60/JRE
Default locale: en, platform encoding: ISO8859-1
OS name: "openvms", version: "v8.4", arch: "ia64", family: "openvms"
bash$
But I don't know why the maven build did not package this two files into my tar.gz or zip file.
Josef
-----Ursprüngliche Nachricht-----
Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
Gesendet: Montag, 7. Januar 2013 14:56
An: Maven Users List
Betreff: Re: building from latest trunk
Not an answer for you but an FYI: Maven trunk has moved to git
On 7 January 2013 13:47, Stadelmann Josef < josef.stadelmann@axa-winterthur.ch> wrote:
> Hi,
>
> I did
> openVMS>
> bash$ svn co trunk
> bash$ mvn clean install
> bash$
>
> all the build steps indicates SUCCESS; lets do a cd and inspect
>
> bash$ cd
> /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT
> bash$ ls -l
> total 10205
> -rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12
> apache-maven-3.1-SNAPSHOT-bin.tar.gz
> -rwxr-x--- 1 STADELMA 129 5234859 Jan 7 12:12
> apache-maven-3.1-SNAPSHOT-bin.zip
> -rwxr-x--- 1 STADELMA 129 1113 Jan 7 12:12
> apache-maven-3.1-SNAPSHOT-site.xml
> -rwxr-x--- 1 STADELMA 129 5569 Jan 7 12:12
> apache-maven-3.1-SNAPSHOT.pom
> -rwxr-x--- 1 STADELMA 129 316 Jan 7 12:12
> maven-metadata-local.xml
>
> openVMS> copy apache-maven-3.1-SNAPSHOT-bin.tar.gz sys$login:
> apache-maven-3.1-SNAPSHOT-bin.tar.gz
> openVMS> set def sys$login
> openVMS>bash
> bash$ gnutar -vzxf apache-maven-3.1-SNAPSHOT-bin.tar.gz
>
> and I get the just built maven-3.1-snapshot installed
>
> BUT
> Now I am facing one problem I've never seen before.
> ***************************************************
>
> bash$ cd $HOME/apache-maven-3.1-SNAPSHOT bash$ ls -l total 13
> -rwxr-x--- 1 STADELMA 129 230 Jan 7 12:12 m2.conf
> -rwxr-x--- 1 STADELMA 129 6152 Jan 7 12:12 mvn.bat
> -rwxr-x--- 1 STADELMA 129 6306 Jan 7 12:12 mvnDebug.bat
>
> I am facing the following problem!
> why was mvn and mvnDebug (the shell files) not packaged into my target
> *tar.gz file?
>
> lets look at the sources
>
> openVMS> set def
> DKA3:[SW-PROJEKTE.asf.maven.maven-3.trunk.apache-maven.src.bin]
> bash$ ls -l
> total 31
> drwxr-x--- 1 STADELMA 129 512 Oct 30 16:27 _svn
> -rwxr-x--- 1 STADELMA 129 222 Oct 30 16:27 m2.conf
> -rwxr-x--- 1 STADELMA 129 5807 Jan 7 11:28 mvn
> -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvn.bat
> -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvnDebug
> -rwxr-x--- 1 STADELMA 129 6106 Jan 7 11:28 mvnDebug.bat
> -rwxr-x--- 1 STADELMA 129 6115 Jan 7 11:28 mvnyjp
>
> bash$
>
> all there, just not packaged with my tar.gz and maybe .zip file
>
> any hints welcome
> Josef
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: building from latest trunk
Posted by Stephen Connolly <st...@gmail.com>.
Not an answer for you but an FYI: Maven trunk has moved to git
On 7 January 2013 13:47, Stadelmann Josef <
josef.stadelmann@axa-winterthur.ch> wrote:
> Hi,
>
> I did
> openVMS>
> bash$ svn co trunk
> bash$ mvn clean install
> bash$
>
> all the build steps indicates SUCCESS; lets do a cd and inspect
>
> bash$ cd /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT
> bash$ ls -l
> total 10205
> -rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12
> apache-maven-3.1-SNAPSHOT-bin.tar.gz
> -rwxr-x--- 1 STADELMA 129 5234859 Jan 7 12:12
> apache-maven-3.1-SNAPSHOT-bin.zip
> -rwxr-x--- 1 STADELMA 129 1113 Jan 7 12:12
> apache-maven-3.1-SNAPSHOT-site.xml
> -rwxr-x--- 1 STADELMA 129 5569 Jan 7 12:12
> apache-maven-3.1-SNAPSHOT.pom
> -rwxr-x--- 1 STADELMA 129 316 Jan 7 12:12
> maven-metadata-local.xml
>
> openVMS> copy apache-maven-3.1-SNAPSHOT-bin.tar.gz sys$login:
> apache-maven-3.1-SNAPSHOT-bin.tar.gz
> openVMS> set def sys$login
> openVMS>bash
> bash$ gnutar -vzxf apache-maven-3.1-SNAPSHOT-bin.tar.gz
>
> and I get the just built maven-3.1-snapshot installed
>
> BUT
> Now I am facing one problem I've never seen before.
> ***************************************************
>
> bash$ cd $HOME/apache-maven-3.1-SNAPSHOT
> bash$ ls -l
> total 13
> -rwxr-x--- 1 STADELMA 129 230 Jan 7 12:12 m2.conf
> -rwxr-x--- 1 STADELMA 129 6152 Jan 7 12:12 mvn.bat
> -rwxr-x--- 1 STADELMA 129 6306 Jan 7 12:12 mvnDebug.bat
>
> I am facing the following problem!
> why was mvn and mvnDebug (the shell files) not packaged into my target
> *tar.gz file?
>
> lets look at the sources
>
> openVMS> set def
> DKA3:[SW-PROJEKTE.asf.maven.maven-3.trunk.apache-maven.src.bin]
> bash$ ls -l
> total 31
> drwxr-x--- 1 STADELMA 129 512 Oct 30 16:27 _svn
> -rwxr-x--- 1 STADELMA 129 222 Oct 30 16:27 m2.conf
> -rwxr-x--- 1 STADELMA 129 5807 Jan 7 11:28 mvn
> -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvn.bat
> -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvnDebug
> -rwxr-x--- 1 STADELMA 129 6106 Jan 7 11:28 mvnDebug.bat
> -rwxr-x--- 1 STADELMA 129 6115 Jan 7 11:28 mvnyjp
>
> bash$
>
> all there, just not packaged with my tar.gz and maybe .zip file
>
> any hints welcome
> Josef
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
AW: building from latest trunk
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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 they are provided in the sources.
This files are required with each unix release in the tar.gz file. And we need it on OpenVMS as maven runs under bash$ a Unix shell.
Any idea why this files are not delivered any longer? or is this now a platform dependent issue?
i.e. if OpenVMS do not include them???
Josef
-----Ursprüngliche Nachricht-----
Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
Gesendet: Montag, 7. Januar 2013 14:47
An: Maven Users List
Betreff: building from latest trunk
Hi,
I did
openVMS>
bash$ svn co trunk
bash$ mvn clean install
bash$
all the build steps indicates SUCCESS; lets do a cd and inspect
bash$ cd /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT
bash$ ls -l
total 10205
-rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12
apache-maven-3.1-SNAPSHOT-bin.tar.gz
-rwxr-x--- 1 STADELMA 129 5234859 Jan 7 12:12
apache-maven-3.1-SNAPSHOT-bin.zip
-rwxr-x--- 1 STADELMA 129 1113 Jan 7 12:12
apache-maven-3.1-SNAPSHOT-site.xml
-rwxr-x--- 1 STADELMA 129 5569 Jan 7 12:12
apache-maven-3.1-SNAPSHOT.pom
-rwxr-x--- 1 STADELMA 129 316 Jan 7 12:12
maven-metadata-local.xml
openVMS> copy apache-maven-3.1-SNAPSHOT-bin.tar.gz sys$login:
apache-maven-3.1-SNAPSHOT-bin.tar.gz
openVMS> set def sys$login
openVMS>bash
bash$ gnutar -vzxf apache-maven-3.1-SNAPSHOT-bin.tar.gz
and I get the just built maven-3.1-snapshot installed
BUT
Now I am facing one problem I've never seen before.
***************************************************
bash$ cd $HOME/apache-maven-3.1-SNAPSHOT bash$ ls -l total 13
-rwxr-x--- 1 STADELMA 129 230 Jan 7 12:12 m2.conf
-rwxr-x--- 1 STADELMA 129 6152 Jan 7 12:12 mvn.bat
-rwxr-x--- 1 STADELMA 129 6306 Jan 7 12:12 mvnDebug.bat
I am facing the following problem!
why was mvn and mvnDebug (the shell files) not packaged into my target *tar.gz file?
lets look at the sources
openVMS> set def
DKA3:[SW-PROJEKTE.asf.maven.maven-3.trunk.apache-maven.src.bin]
bash$ ls -l
total 31
drwxr-x--- 1 STADELMA 129 512 Oct 30 16:27 _svn
-rwxr-x--- 1 STADELMA 129 222 Oct 30 16:27 m2.conf
-rwxr-x--- 1 STADELMA 129 5807 Jan 7 11:28 mvn
-rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvn.bat
-rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvnDebug
-rwxr-x--- 1 STADELMA 129 6106 Jan 7 11:28 mvnDebug.bat
-rwxr-x--- 1 STADELMA 129 6115 Jan 7 11:28 mvnyjp
bash$
all there, just not packaged with my tar.gz and maybe .zip file
any hints welcome
Josef
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org