-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
For some reason, it looks we're compiling test classes twice. Here's an edited excerpt of a build:
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ magnolia-resource-loader --- [...] [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ magnolia-resource-loader --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 25 source files to /Users/gjoseph/Dev/magnolia/git/magnolia_main-clean-2/magnolia-resource-loader/target/classes [...] [INFO] [INFO] --- maven-compiler-plugin:3.2:testCompile (compile-tests) @ magnolia-resource-loader --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 11 source files to /Users/gjoseph/Dev/magnolia/git/magnolia_main-clean-2/magnolia-resource-loader/target/test-classes ^--- first testCompile [...] [INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ magnolia-resource-loader --- [...] [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ magnolia-resource-loader --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 11 source files to /Users/gjoseph/Dev/magnolia/git/magnolia_main-clean-2/magnolia-resource-loader/target/test-classes ^--- second testCompile ! [...] [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ magnolia-resource-loader ---
At first sight, it'd look like the first compile is with a custom execution of the plugin that we do, while the second one uses the default-testCompile execution.
Acceptance criteria
