Maven编译器插件，构建帮助器插件不会生成类文件

Question

I am trying to convert an existing project into a maven project. It has 3 modules and one of the modules has multiple source folders. http://i.imgur.com/jZCnR.png

A maven clean and install or an eclipse clean does not create the class files in the classes and test-classes folder. The project structure gets created by there are no class files there.

The following plugin configuration is defined in the parent pom.

<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>build-helper-maven-plugin</artifactId>
    <version>1.7</version>
    <executions>
        <execution>
            <id>add-source</id>
            <phase>generate-sources</phase>
            <goals><goal>add-source</goal></goals>
            <configuration>
                <sources>
                    <source>src/main/java/**/*.*</source>
                    <source>src/report/java/**/*.*</source>
                    <source>src/architect/java/**/*.*</source>
                </sources>
            </configuration>
        </execution>
        <execution>
            <id>add-test-source</id>
            <phase>generate-test-sources</phase>
            <goals><goal>add-test-source</goal></goals>
            <configuration>
                <sources>
                    <source>src/test/java/**/*.*</source>
                </sources>
            </configuration>
        </execution>
    </executions>
</plugin>
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <version>3.0</version>
    <configuration>
        <source>1.7</source>
        <target>1.7</target>
        <debug>false</debug>
    </configuration>
    <executions>
        <execution>
            <id>default-compile</id>
            <phase>compile</phase>
            <goals><goal>compile</goal></goals>
            <configuration>
                <includes>
                    <include>src/main/java/**/*.*</include>
                    <include>src/report/java/**/*.*</include>
                    <include>src/architect/java/**/*.*</include>
                </includes>
            </configuration>
        </execution>
        <execution>
            <id>default-testCompile</id>
            <phase>test-compile</phase>
            <goals><goal>testCompile</goal></goals>
            <configuration>
                <testIncludes>
                    <include>src/test/java/**/*.*</include>
                </testIncludes>
            </configuration>
        </execution>
    </executions>
</plugin>

What am I doing wrong?

Answer 1

For me the mvn plugin in eclipse doesn't generate the proper structure either. Try running mvn eclipse:eclipse in cmd. That did it for me.

Also you used the phase 'generate-test-sources'. This doesn't seem to work try 'generate-sources'.

Answer 2

According to Using MOJO build-helper-maven-plugin to add more source folders to MAVEN you should not define additional source directories again via the includes tag; define them just in build-helper-maven-plugin and that is it.

Also you can try to associate add-source goal with an earlier Maven phase, like initialize . Generally, the earlier the better.

<phase>initialize</phase>
<goals>
    <goal>add-source</goal>
</goals>

In my case, my mistake it was to bind it to compile phase. Despite my build-helper-maven-plugin was defined before maven-compile-plugin in the pom.xml , somehow default-compile task kicked in first and silently ignored my extra source directories causing some unexpected errors further down the build. Order of steps bonded to same phase should follow order of appearance in pom.xml but, well, not always.

Check that you see in your log:

[INFO] --- build-helper-maven-plugin:1.8:add-source (add-gen-source) @ deepclone-sample-project-1 ---
[INFO] Source directory: E:\dev\workspace...\src\main\generated added.

Handy trick: Make a deliberate error in your code, just to check that compiler really go through you extra directories. If compilation does not fail instantly then the issues in not about not generating class files files but really about compiler configuration. You can exclude incremental build issues or similar more esoteric issues.

Answer 3

作为记录在建立帮助Maven插件的add-source目标，应指定目录中的<source>标签。