After some experimentation I still couldn't detect any errors showing up, however, I did remember I noticed some strange anomalies after using dependency:purge-local-repository the other day - where that goal seems to delete all the local artifacts, doesn't clean up any of the meta-data files in the .m2 repository, which triggers problems with version range based builds ( such as my integration build here ) when metadata exists for files that don't.
After I rm -rf'd my entire .m2/repository/mygroupidhere directory and watched maven download 400 odd pom versions everything seemed to work fine. So I suspect this is more an issue with the dependency plugin trashing things more than aether, but maybe aether could be more graceful around broken metadata. If I get some time in the morning/weekend I'll see if I can setup a broken ./m2 setup and a test project to reproduce. -- Mark Derricutt — twitter — podcast — blog — google+ On 19/09/2013, at 1:09 PM, Jason van Zyl <ja...@tesla.io> wrote: > If you can reproduce it in a stand-alone example I can track it down. Or if > it's an OSS project I'll take a look.
signature.asc
Description: Message signed with OpenPGP using GPGMail
