Quoting "Werner Guttmann" <[EMAIL PROTECTED]>:
(...)
That's odd, as this basically does a SVN checkout behind the scenes,
packages the files obtaind and ships it to you. (...)
Well if you want to amuse yourself, have a look at
http://ayaken.net/mvn.log
(which is result of running mvn -e clean install > ..\mvn.log in trunk dir).
java is:
...\Desktop\trunk>java -version
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
maven is:
...\Desktop\trunk>mvn --version
Maven version: 2.0.9
Java version: 1.6.0_10
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Next steps: pack up a unit test case triggering the problem that made
me want to build it in the first place and test your suggested
solution (using a mapping file although I'm pretty confident that
that'll work -- it'll remove the clashes which you produce, so why
should it fail?) although I still think the real bug is that you
produce clashing symbols in the first place.
Regards,
-Martin
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
