Thanks Baptiste. Seems this is the only workable solution so far... Might do it that way :)
(Just curious; since Maven is already able to detect this "error" why couldn't we implement a real error for that? But i guess, i know to less to cite that; dunno if that would break a clean multimodule build, or other things...) Anyway... thanks :) brgds Myron Am 13.03.2013 07:24, schrieb Baptiste MATHUS: > Hi, > A good CI practice is to 1) use a private local tell/cache per job and 2) > wipe out the local cache regularly (say once a day, or maybe a week to > begin with) > > Note that wiping out the local repo is also recommended on your workstation > on a regular basis for the exact reason you speak about. > > Cheers > Le 12 mars 2013 18:38, "Myron" <[email protected]> a écrit : > >> Hi All, >> >> is it in any way possible to FAIL a maven build when the snapshot update >> fails? Currently, the local snapshot is used silently (forever?)... >> >> Use case: >> Update snapshot setting is set to "always"; >> parent artifact gets released, parent snapshot will be cleaned by nexus >> job. >> But child artifact continues to build successfully forever with old >> snapshot parent on buildserver... (but not on a fresh checkout) >> >> >>> Parsing POMs >>> Failed to transfer Could not find metadata >> com.mycompany:parent:1.1.1-SNAPSHOT/maven-metadata.xml in nexus[...] >>> Modules changed, recalculating dependency graph >>> [...] >> >> YES, i could set the Jenkins job to always use a private/clean >> repository (at the cost of n^x disk space), but... isn't there a >> better/easier way to archive that? with a parameter like 'force update'? >> (Does the "maven validation level" help in any way?) >> >> How do you handle this?! >> >> brgds >> Myron >> >> --------------------------------------------------------------------- >> 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]
