[ http://jira.codehaus.org/browse/MCOMPILER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209238#action_209238 ]
Jakob Magiera edited comment on MCOMPILER-30 at 2/5/10 7:38 AM: ---------------------------------------------------------------- @Hilal Ram This doesn't solve the issue, because maven is not actually executing the javac you specified but the internal compiler of the jdk that is set in your java_home. Think about it, it doesn't make sense to specify an executable if you are not going to fork a new process. was (Author: jmagiera): @Hilal Ram This doesn't solve the issue, because maven is not actually executing the javac you specified but whatever is set in your java_home. Think about it, it doesn't make sense to specify an executable if you are not going to fork a new process. > Compiler fork executable fails when the path has spaces > ------------------------------------------------------- > > Key: MCOMPILER-30 > URL: http://jira.codehaus.org/browse/MCOMPILER-30 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Carlos Sanchez > > JAVA_1_3_HOME=C:\Program Files\Java\jdk1.3.1_18 > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <configuration> > <fork>true</fork> > <compilerVersion>1.3</compilerVersion> > <executable>${JAVA_1_3_HOME}/bin/javac</executable> > </configuration> > </plugin> > Fails with > Failure executing javac, but could not parse the error: > 'C:\Program' is not recognized as an internal or external command, > operable program or batch file. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira