|Subject:||RE: Recent windows batch file changes|
|Date:||Dec 1, 2002 2:41:15 pm|
I'd rather we didn't apply this patch.
The issue is that the xml-apis jar file we have is bad.
We shouldn't (and don't need) the flags passed to Maven.
We also don't need the piccolo specific code in various classes.
I'm waiting on someone getting back to me re: the current xml-apis version so that all of this will be resolved.
Aslak Hellesoy <asla...@netcom.no> wrote on 02/12/2002 07:41:45 AM:
I have experienced some problems with the combo Xerces/j2sdk1.4.1_01. It's a java.lang.ClassNotFoundException during the xdoc:transform-user-docs goal.
I have submitted a patch for maven/maven.bat that should fix it: http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-166
I added some features tonight to the windows batch file in CVS.
1) Echo ON/OFF as an optional environment variable.
You can now set the environment variable 'ECHO' to a value and that will be used in the batch file. If it's not set, ECHO will remain OFF Sample:
Will cause all batch commands to be displayed.
2) Pause at the end of the batch file is enabled via an Environment variable
Set the environment variable 'PAUSE' to a value and the batch file will pause before finishing. This is handy when launching from explorer or a shortcut. Sample:
Will cause the batch file to pause at the end waiting for a key stroke.
3) User provided options to Maven's JVM
Set the environment variable 'MAVEN_OPTS' to a value, and it will be passed to the JVM on the command line *after* the standard maven options, hence overriding the defaults. This is handy when you want to pass some extra parameters to the JVM/Maven and don't want to hack your own batch file. Sample:
Set MAVEN_OPTS=-Xdebug -Xnoagent -Djava.compiler=NONE Set MAVEN_OPTS=%MAVEN_OPTS% -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000
Sets up Maven in debug mode, waiting for you to attach to it from your debug session.
-- To unsubscribe, e-mail: