Ok, I will try to find out, but have to put it to the working queue. I will open a ticket as reminder.
Martin Am 20. Oktober 2016 04:06:34 MESZ, schrieb Olivier Lamy <[email protected]>: >Hi Martin >I think archiva-proxy is/was dependent on maven2-repository. >But I'm not sure as maybe it's not anymore the case :-) ). >So I should say have a try? > >On 18 October 2016 at 07:42, Martin <[email protected]> wrote: > >> Hi, >> >> stumbled over the issue MRM-1926 after I found some invalid checksum >files >> in >> one of my own repositories. >> I think I have fixed it, but there are parts of the code that seem to >be >> redundant (downloading the artifacts). >> >> org/apache/archiva/metadata/repository/storage/maven2/ >> RepositoryModelResolver.java:226 >> >> I found this comment: >> // FIXME: we need to do some refactoring, we cannot re-use the >proxy >> components of archiva-proxy in maven2-repository >> // because it's causing a cyclic dependency >> private boolean getModelFromProxy( RemoteRepository >remoteRepository, >> String groupId, String artifactId, >> String version, String >filename ) >> >> >> Do you know what's the cause of this cyclic dependency here? >> I just like to understand and maybe keep a reminder that there is >something >> that should be changed. >> >> And currently it's not obvious to me why there are to places where >> artifacts >> are downloaded from remote repositories. Do you know in which cases >the >> ModelResolver downloads the artifact and when the ProxyConnector? >> >> Greetings >> >> Martin >> >> >> > > >-- >Olivier Lamy >http://twitter.com/olamy | http://linkedin.com/in/olamy -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
