Question

I have a Maven project within which I need execute two code generation steps. One generates some Java types, then the second depends on those Java types to generate some more code. Is there a way to have both of these steps happening during my build?

At the moment my steps are:

1. execute first code generation plugin (during generate-sources)
2. add directory of generated types to build path
3. execute second code generation plugin (during compile)

However my problem is that anything generated by the second code generation plugin will not be compiled (because the compile phase has finished). If I attach the second code generation plugin to an earlier phase, it fails because it needs the classes from the first code generation plugin to be present on the classpath.

I know I could split this into two modules with one dependent on the other, but I was wondering if this could be achieved in one pom. It seems like a need a way to invoke compile again after the normal compile phase is complete.

Any ideas?

Answer 1

You can always configure two executions of the compiler plugin, both tied to the compile phase. In one you include the extra stuff:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-compiler-plugin</artifactId>
  <version>2.3.2</version>
  <executions>
    <execution>
      <id>one</id>
      <phase>compile</phase>
      <goals>
        <goal>compile</goal>
      </goals>
      <configuration></configuration>
    </execution>  
    <execution>
      <id>two</id>
      <phase>compile</phase>
      <goals>
        <goal>compile</goal>
      </goals>
      <configuration>
      <compilerArgument>-verbose -bootclasspath ${java.home}\lib\rt.jar</compilerArgument>
      </configuration>
    </execution>
  </executions>
<plugin>

You may try as well <includes><include>path/</include></includes>

According the official documentation:

When multiple executions are given that match a particular phase, they are executed in the order specified in the POM, with inherited executions running first.

But I quite not get what you exactly want.
http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html