[joke]
If you're really stuck I can invoke a claim that we agreed X and we can
rely on everyone else being too lazy to find the counter-evidence on the
mailing list archives!
[/joke]
More seriously, I remember a discussion but my memory fails me on the exact
version we settled on... Anything less
The reason why you're not sure of the exact version explains why we ended
up with simply 3.0 :)
Now it is clear for everybody.
Robert
Op Wed, 15 Jul 2015 08:43:59 +0200 schreef Kristian Rosenvold
:
14. jul. 2015 21.04 skrev "Robert Scholte"
mvn clean verify -Prun-its -Dinvoker.mavenHome=
Github user dsyer commented on the pull request:
https://github.com/apache/maven/pull/58#issuecomment-122027101
My reading of the windows script is it works already (but it's harder to
tell with batch scripts, for me at least).
---
If your project is set up for it, you can reply to t
Github user agudian commented on the pull request:
https://github.com/apache/maven/pull/58#issuecomment-121962243
Hi,
Thanks for the patch!
Are the windows-scripts also affected by the bug and could use a fix?
---
If your project is set up for it, you can reply to t
GitHub user dsyer opened a pull request:
https://github.com/apache/maven/pull/58
Locate .mvn in current directory
There was a problem with the logic in the while loop that detects
the base dir - it should first look in the current directory,
otherwise you can't build in a dir
Github user dsyer commented on the pull request:
https://github.com/apache/maven/pull/49#issuecomment-121934925
It looks like `$MAVEN_CONFIG` is already used to prepend to the command
line arguments. Isn't that enough? There is no comment or any other usage of
`$MAVEN_CONFIG` so it's
