Hello, I work on a complex project, having many modules. I added one module M inside the existing hierarchy A.B. This M makes use of different other modules at specific places in the project A hierarchy. (usually guided by eclipse editor assistance that certain classes are to be imported, or compiler errors that informed me to add a dependency in the M's pom.xml). B's pom.xml is updated as having a new module M.
>From the command line: cd A mvn -X -s maven_settings.xml reactor:make -Dmake.goals=test -Dmake.folders=B/M >maven.log -> It runs also tests from other modules. I feel it should only run tests for module M? Running this command a second time, it re-compiles everything again. Why does the make system not see the sources have not been changed? Or is my command line wrong? mvn -X -s maven_settings.xml reactor:make-dependents -Dmake.goals=test -Dmake.folders=B/M >maven.log -> Starts compiling and then fails on certain modules due to snapshots not being found. But these failing modules are available as source, can be correctly compiled as classes, are even used this way with the command above. Then why does it need these jars if it fails retrieving these jars. Is there a command to make and store these jars in our own repository/portal? Actually, there are no modules depending on M, why is the compilation failing? >From within eclipse GUI: I don't seem to be use m2eclipse in a working way. It is also not clear when maven is taken over command from eclipse (e.g. doing a 'build ...'). I feel it does not seem to behave consistent. It usually fails when trying to get snapshots from the portal. I like to understand these jar/snapshot problem above because I see this error related to the jars/snapshot also within the eclipse GUI environment under some circumstances: Right click on the module M in the project explorer. In this menu I see "Debug as ..." Intuitively I guess that does all actions for a debug build. I can now choose "JUnit Test" -> long time nothing happens Then it reports "Class not found com.orig.B.M.TestFileImport" When I choose "Maven test". -> I get the snapshot error. Is there a way around this? Sorry for the long email and questions ... Kind regards, francis --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
