I forgot to mention that keeping this check in a unit test is probably not very reliable anyway if you have good developers in your team. A good developer refactors test code along with the production code. ;-) -- Alexander Kriegisch
> Am 07.04.2015 um 06:08 schrieb Alexander Kriegisch <[email protected]>: > > Quick and dirty? Keep a SHA-1 checksum of the pom in your unit test and > compute it. You can also grep the dependencies section and normalise > whitespace first. This would not be stable against change of order or > refactoring using properties for version numbers etc., but you wanted > something easy. ;-) > -- > Alexander Kriegisch > > >> Am 07.04.2015 um 05:18 schrieb Kevin Burton <[email protected]>: >> >> I have a few modules that I want to lock down so that I can easily keep >> track of dependencies over time. >> >> This way if a developer adds a new dependency, the test will immediately >> break and someone will have to approve the change. >> >> Is this possible? Could I embed this in a unit test or does it have to be a >> plugin? ideally something easy… >> >> -- >> >> Founder/CEO Spinn3r.com >> Location: *San Francisco, CA* >> blog: http://burtonator.wordpress.com >> … or check out my Google+ profile >> <https://plus.google.com/102718274791889610666/posts> >> <http://spinn3r.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]
