There is only one way I could see of this happening... If some ***idiot*** has decided that the parent project being installed in the local repo is a bad plan and configured the install plugin in the parent to skip... which then gets picked up by all the children... never mind that you then cannot build them independently if your local repo gets wiped... and the local repo would probably have the old version before the install skip was turned on... which could explain why a single module installs correctly (as it would be resolving the old parent from the local repo and not the one with skip from the reactor)
-Stephen On 10 August 2011 09:38, Anders Hammar <[email protected]> wrote: > I very much doubt this. > When build, check the console output for the install plugin. It will say > where it is installing the artifacts. I've never heard of a case where this > would not work (unless you get some very clear error in the console). > > /Anders > > On Wed, Aug 10, 2011 at 09:46, manukm07 <[email protected]> wrote: > >> I have a multimodule project and when I do a "clean install" from root >> directory, the artifact jars are created in the target directory of the >> submodule, but not getting copied to localrepository. The issue is there >> even if I skip the test cases using "-DskipTests=true" option. >> But the same artifacts will be copied to local repository, if i do a >> "clean >> install" from individual modules. >> -- >> Manu >> >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/Artifacts-not-getting-installed-in-local-repository-tp4684962p4684962.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] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
