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]
