Brett, So I did some more digging, and found your custom wagon implementation that can manage storage and retrieval of artifacts via CVS or Subversion.
http://blogs.codehaus.org/people/brett/archives/001066_storing_your_maven_repository_in_cvssubversion.html Perhaps we could also create a custom wagon implementation, similar to the FileWagon, but resolve the dependencies from a project-relative location? How does one register such a custom wagon implementation with Maven2? This would seem to have the downside of copying the artifact from the project-relative location to the local repository cache in the user's homedir, but it's a start - and it's probably a smaller delta from this to using Maven2 with a real central repository. Kind Regards, John Fallows. On 5/27/05, Brett Porter <[EMAIL PROTECTED]> wrote: > (copying to users list for the record) > > On 5/27/05, John Fallows <[EMAIL PROTECTED]> wrote: > > Hi Brett, > > > > I understand. What I'm asking for is for Maven2 to make the > > "dependency resolver" API pluggable, so that we can configure our > > projects to use a custom implementation of a common API, without > > needing to compile a custom Maven2 build, and making it much easier to > > uptake new Maven2 releases. > > > > Our corporate version control solution delivers the JARs along with > > the source as a unified "view". Although the implementation is > > different, you can think of it as though the JARs were checked in to > > source control. > > > > Right now, we have a mixture of Makefiles and Ant build scripts that > > reference these JARs using project-relative paths so that the builds > > are self contained. > > > > We would need to replace the "dependency resolver" implementation to > > map each [groupId, artifactId, version] to a project-relative path, > > pointing at each "checked-in" JAR. We do not need automatic > > transitive dependency resolution, nor automatic download of > > dependencies. We would trigger build failure if a dependency in the > > POM was not mapped locally. > > > > Kind Regards, > > John Fallows. > > > > On 5/27/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > Can you detail more about your custom solution, and what it does? > > > > > > As you'll see from our comments, because this does away with a whole > > > lot of Maven's features what you'd be faced with is probably > > > recompiling your own Maven distribution from source, with your own > > > resolver implementation (it shouldn't require any changes to Maven's > > > code, just the configuration). > > > > > > - Brett > > > > > > On 5/27/05, John Fallows <[EMAIL PROTECTED]> wrote: > > > > Hey Brett, > > > > > > > > I commented on the doc at > > > > > > > > http://docs.codehaus.org/display/MAVEN/Custom+Repository+or+Resolver+Implementations > > > > > > > > In short, we can live without transitive dependencies, since we want > > > > to control every single dependency ourselves. > > > > > > > > Kind Regards, > > > > John Fallows. > > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
