Hi, For a client we did this: - have an Archiva running on one developper's desktop - have the directory in which archiva stores the artifact in version control (that developper was responsible for adding to the version control what archiva had downloaded) - have all the other developpers setting ther mirrorOf central to the svn repository of archiva's directory - when an artifact is not found, temporarily change its mirrorOf central to point to the real archiva and notify the developper that he should commit the archiva's changes.
This worked fine. we where around 15 developpers in the project. Regards, Raphaël 2008/3/10, Marco Mistroni <[EMAIL PROTECTED]>: > hi all, > was wondering if someone has any ideas or had to deal with similar cases. > > my colleague and i are trying to promote maven at our working place.... > using an internal repository > > the problem is that people here want to store artifact / external libraries > in svn rather than in an internal repository > > only thing i could think was to store the maven repository in svn and check > it out every time, pointing maven to > look at the localRepository in my custom directory > > i was not able to find any maven proxy (either Proximity or Artifactory) > that are linked to svn.. > > anyone has any suggestions/comments? > > thanks in advance and regards > > marco >
