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. 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. Anyway, you already found two good solutions to your problem. This kind of war is nonsense IMHO. Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
