Thanks for your answer, Wayne. I'll refrain from using Nabble's formatting options from now on. Here are the informations from my first message, in plain text this time.
=== === === My project has a basic multi-module structure, like this : project |_project-core |_project-web |_project-batch The thing is, I get two different results for executing mvn clean package, whether I run it from project-core or from project. >From project-core [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ profilage-core --- [INFO] Building jar: D:\ozp6kz\Mes Documents\eclipse_workspace\ProjetProfilage\profilage-core\target\profilage-core-0.1.jar >From project [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ profilage-core --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: D:\ozp6kz\Mes Documents\eclipse_workspace\ProjetProfilage\profilage-core\target\profilage-core-0.1.jar [INFO] Basically, as a stand-alone, the project builds perfectly well, which allows in turn the other modules to build correctly. But when built as part of the global, multi-module project, there's this one [WARNING] line which throws off the rest of the build. === === === When preparing my code for paste-bins, I (finally) noticed the difference between the two builds. It happens during the execution of dependency:purge-local-repository. As you can see in the "build" pastebins below, there's only one library affected (profilage-lse). But, it's re-downloaded once during the standalone build, and twice during the "multi-module" build. Might seem benign, but when I comment out the execution for that goal, the warning disappears, and the "multimodule" build is successful. I'm definitely at a loss as to why this happens, so any explanation would be greatly appreciated ! Here are the pastebins from poms and builds, expurged of information unrelated : pom.xml - core module : http://commitcode.com/p/r/57wI2E5ovTY.html pom.xml - project parent : http://commitcode.com/p/r/57wI4xQmdLk.html pom.xml - corporate parent : http://commitcode.com/p/r/xX96TKUHndS.html pom.xml - help:effective-pom : http://commitcode.com/p/r/57wI8D7a2eV.html build - standalone : http://commitcode.com/p/r/xX97siekqj5.html build - as a module : http://commitcode.com/p/r/57wIbt2oV2v.html Philippe -- View this message in context: http://maven.40175.n5.nabble.com/Different-behavior-when-building-a-project-as-a-module-or-stand-alone-tp5607081p5611840.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
