(skipping the ones you're going to look at in the issue) On 13/04/2011, at 8:11 AM, Josimpson Ocaba wrote:
> >> >> About r1045023: >> >>> On 10/01/2011, at 1:46 PM, Josimpson Ocaba wrote: >>> >>>> This was added for the other remote repositories, because they were just >> skipping the >>>> other remote repositories and were not actually trying to resolve from >> their locations. >>> >>> This was breaking several integration tests, or is there a specific one >> to illustrate the >>> case? >>> >>> My point is that these tests worked in 1.2.1. Repeating this check >> doesn't look like the best >>> way to accommodate the removal of the UAC because it will mean repeated >> resolution, which >>> was a performance problem in the past. >>> >>> Am I missing something? >> >> The dependencies were not getting resolved anymore. This may need to be > revisited for performance enhancement again, but the fix that was already in > place did not allow all of the remote repositories in settings.xml to be > looked up. Hence certain repositories containing the dependencies were > skipped. Is there an IT to exercise this, so we can see it failing before the fix is in place? I think there must be a better way to do it - though we can balance the amount of time against just removing RDF... - Brett -- Brett Porter [email protected] http://brettporter.wordpress.com/
