Missing -d option

[GoogleCodeExporter]

The -d option passed to javac will indirectly set the 
StandardLocation.CLASS_OUTPUT. 

leaving this option makes the StandardLocation.CLASS_OUTPUT to point to the 
root directory(in my case)


Workaround

<compilerArguments>-d ${project.build.outputDirectory}</compilerArguments>
this breaks if there is a space in the path

Original issue reported on code.google.com by ananthakumaran on 21 Jan 2010 at 1:15

[GoogleCodeExporter]

when i used the specified workaround I get following build failure:

javacTask: directory not found: /localdisk/google/jlibs/examples/target/classes

the plugin should create this directory before running javac 

Original comment by santhosh.tekuri@gmail.com on 18 May 2010 at 12:23

[GoogleCodeExporter]

a workaround for a workaround could be use maven-antrun-plugin 
http://maven.apache.org/plugins/maven-antrun-plugin

An example
========
  <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <executions>
          <execution>
            <phase> <!-- a lifecycle phase --> </phase>
            <configuration>
              <tasks>
                   <mkdir dir="${project.build.outputDirectory}"/>
              </tasks>
            </configuration>
            <goals>
              <goal>run</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

Original comment by bartolom...@gmail.com on 18 May 2010 at 12:51

[GoogleCodeExporter]

another possibility is to use the <outputDirectory> configuration parameter of 
plugin. Take note that It is related 
to the generated source file  but , probably, could work well in your case

i'm start to work on this issue

Original comment by bartolom...@gmail.com on 18 May 2010 at 1:16

• Changed state: Started

[GoogleCodeExporter]

i've deployed the release 1.3.5 that fix this issue

the new parameter is <outputClassDirectory> 

take a look to documentation

Original comment by bartolom...@gmail.com on 18 May 2010 at 1:50

• Changed state: Fixed