>-----Original Message----- >From: Antonio Petrelli [mailto:[email protected]] > >2010/11/17 Asmann, Roland <[email protected]>: >> Does anybody have any ideas on how to do this? >> I was thinking about using a preant-POM and the enforcer-plugin, but as >> soon as I make an update, all projects would have to update their >> parents as well -- which is exactly what they don't want, otherwise they >> could've changed the dependencies themselves... >> >> The problem here is that the architecture-department wants to get rid of >> certain artifacts and the developers don't want to update their POMs... >> I know, it's not ideal, but I have to find some sort of solution for >this... > >I'm sorry but I think that magic cannot happen, at least in Maven world. >Either update your parent and encourage developers to change parent >version, or encourage developers to change dependencies. >I mean, if you update parent POM and it is not a SNAPSHOT version, and >child POMs are not connected to this SNAPSHOT, then developers must >change parent POM version.
IMO, there's nothing wrong with using a snapshot version for this. You'll need to update all the individual project poms once to change to the snapshot version, but then you can leave them alone. >You can (very bad! don't do it!) modify the original deployed version >of that parent POM to add those rules, developers should clean their >local repository and redownload the parent POM. Yeah, this causes problems because maven doesn't ever recheck non-snapshot artifacts that are in it's .m2/repository cache. You can't even force it to [*1], so the only option you have it to remove the entire cache. You certainly don't want to make this part of your normal build procedure! eric [*1] which IMO is a bug/missing important feature: it should have a way to verify checksums, to at least be able to detect corrupted files. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
