The following comment has been added to this issue:
Author: Harald Ommang
Created: Fri, 2 Jul 2004 8:15 AM
Body:
This is a duplicate of MAVEN-1354
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1356?page=comments#action_21301
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1356
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1356
Summary: Windows start script fails
Type: Bug
Status: Unassigned
Priority: Trivial
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
cli
Versions:
1.0-rc4
Assignee:
Reporter: Jan Mat�rne
Created: Fri, 2 Jul 2004 8:13 AM
Updated: Fri, 2 Jul 2004 8:15 AM
Environment: Windows 2000 German
Description:
I had installed Maven 1.0RC4 via Windows installer (maven-1.0-rc4.exe). After
installing I had to add %MAVEN_HOME%\bin to the path. When invoking "maven" then I got
an output abouts java invoke syntax. The result: I had to change %HOME% to %HOMEDRIVE%
because trailing backslash lets java not launch.
Error near line 126 in bin/maven.bat.
Changing from
%MAVEN_JAVA_EXE%
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
"-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%"
"-Dtools.jar=%JAVA_HOME%\lib\tools.jar"
"-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf"
-Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH%
%MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS%
to
%MAVEN_JAVA_EXE%
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
"-Duser.home.env=%HOMEDRIVE%" "-Dmaven.home=%MAVEN_HOME%"
"-Dtools.jar=%JAVA_HOME%\lib\tools.jar"
"-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf"
-Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH%
%MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS%
resolved the problem. But I think there are other invocation points ...
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
