Question

Where is the ‘best practice’ place to put @Configuration beans in one’s Spring project? It seems wrong putting config under /src/main/java, but otherwise the classes won’t get compiled.

How do others approach this problem?

Answer 1

It seems that the only solution, if you want to decouple the configuration from the logic, is to add additional source folder to the Maven config:

<project>
  ...
  <build>
    <plugins>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>build-helper-maven-plugin</artifactId>
        <version>1.1</version>
        <executions>
          <execution>
            <id>add-source</id>
            <phase>generate-sources</phase>
            <goals>
              <goal>add-source</goal>
            </goals>
            <configuration>
              <sources>
                <source>src/main/configuration</source>
                ...
              </sources>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
</project>

It seems that this solution will achieve what you want. src/main/configuration will be added to the compilation plugin and will end up in target/classes while, in the project source tree, those will be placed somewhere else.