After having to disable my maven mirror for one reason or another awhile ago I now seem to be getting hit with this rather annoying bug on quite a few projects now that my ~/.m2/repository has a mix of artifacts downloaded via a mirror, and others direct.
rm'ing the _maven.repositories file from ~/.m2/repository seems to work around the problem, but I'm also now hearing from people on IRC who seem to be getting tripped up with the same problem. What can I do to try and help get this problem resolved? By reading Richard's ticket the problem is inside Aether, should we raise the ticket in Aether's github issue tracker or is here good enough ( I seem to recall here being decided as the place to go when Aether was introduced ). Mark PS: For reference, the ticket was http://jira.codehaus.org/browse/MNG-5084 -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On Fri, May 13, 2011 at 8:43 PM, Richard Vowles < [email protected]> wrote: > Hi all, > > I'm not sure of the etiquette here - but I'm struggling with an aether bug > in the easyb project - we can't release our plugin. > > I have a reproducible sample, I have debugged through down the sections of > code which seem to be at fault, but I am not confident enough about the > implications to suggest a fix. > > The bug is listed here: > > http://jira.codehaus.org/browse/MNG-5084 > > It appears I have to completely change the way that artefacts are released > (i.e. not use version ranges) to work around the bug. > > What is the proper method of progressing this? > > Thanks > Richard > > -- > --- > Richard Vowles, > Grails, Groovy, Java > Consistency is the last refuge of the unimaginative - Oscar Wilde > ph: +64275467747, linkedin, skype:rvowles > get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! - > http://tinyurl.com/cmcceh > podcast: http://www.illegalargument.com >
