If I read that right, there is a problem in the shell scripts, not the windows cmd script, right? Because mvnDebug.cmd works for me as expected.
Am Sonntag, 5. April 2015 schrieb Karl Heinz Marbaise : > Hi, > > based on some comments (http://blog.soebes.de/blog/ > 2015/03/17/apache-maven-3-dot-3-1-features/#disqus_thread) on my site it > looks like we have a bug in the debug scripts which do not correctly export > the variables to the underlying mvn scripts... > > mvnDebug.cmd > > @setlocal > > will prevent exporting the environment variable to the sub calling mvn.cmd > file... > > furthermore in mvnDebug the call "env ..." will do the same ? (I'm not > sure about) can someone acknowledge this with more knowledge about this? > > > Kind regards > Karl Heinz Marbaise > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
