I will have a look around the codebase and start working on the design spec around the end of the week if you won't start on it by then.
On Wed, Feb 19, 2014 at 4:06 AM, Daz DeBoer <darrell.deb...@gradleware.com>wrote: > Hey Marcin > That's great. If you want to take a stab at a design spec for supporting > an sftp repository transport, that would be a good start. This can go into > a new document: /design-docs/repository-transports.md. > > For the first story I think it should be sufficient to simply support a > 'sftp://host[:port]' type URL, together with the existing user/password > credentials. But we should probably start thinking about how we can support > other authentication mechanisms as well (for all transports) > > We also need to start thinking about how we're going to provide adequate > test coverage for different repository transports. Do we want to run all of > our remote resolution tests against all remote transports, or choose a > subset of tests that would be sufficient for demonstrating a particular > transport behaves correctly? We can probably come up with > a org.gradle.integtests.fixtures.AbstractMultiTestRunner subclass that can > run a set of tests against a defined set of transports. > > I'll try to start on a design spec sometime this week, but if you want to > dive in and get started, that would be great. > cheers > Daz > > > > On Tue, Feb 18, 2014 at 12:15 PM, Marcin Erdmann < > marcin.erdm...@proxerd.pl> wrote: > >> I would be interested in implementing this. I was wondering some time ago >> if I could use gradle to resolve/publish dependencies from/to S3. If I work >> on this I could learn how/if that requirement could be implemented in the >> future. >> >> Where shall I start? >> >> >> On Mon, Feb 17, 2014 at 12:50 AM, Daz DeBoer < >> darrell.deb...@gradleware.com> wrote: >> >>> G'day >>> >>> Currently, the 'maven' and 'ivy' repository implementations only support >>> publishing and resolving via HTTP, HTTPS and local file system. To use >>> SFTP, SSH or any other protocol, users currently need to revert to using a >>> custom Ivy resolver to provide this functionality. Since we've deprecated >>> this mechanism, it would be great to add native support for different >>> protocols to the 'ivy' and 'maven' repositories. Support would be useful >>> for dependency resolution, as well as for publishing via the new publishing >>> plugins. >>> >>> We're wondering if there's any person or group out there who wants to >>> take this on? The nice thing about this enhancement is that it's relatively >>> self-contained. There will however, be a significant number of new tests >>> required, together with some test infrastructure to allow us to validate >>> these protocols (we already have infrastructure for testing SFtp). >>> >>> The implementation will likely involve: >>> >>> - Adding new RepositoryTransport implementations for SFtp and SSH. >>> (Possibly WebDav too). >>> - Improving the way we select a RepositoryTransport implementation >>> based on the repository URL(s). >>> - Adding integration tests for resolving from and publishing to both >>> ivy and maven repositories with the new protocols (publishing via new >>> publishing plugins). >>> >>> If you're seriously interested in taking on this project, please let us >>> know and we can start working together on a design document and discussing >>> implementation possibilities. >>> Thanks for your consideration. >>> cheers >>> Daz >>> >> >> >
