SvnResolver anyone?

[Adrian Woodhead <ad...@last.fm>]

Hey there,

I mailed this list a few weeks back with some questions about writing a 
custom Ivy resolver which uses Subversion to store artifacts. Well, I 
have done this using the code from your 2.0 alpha release and we are now 
using it actively to retrieve and publish files to and from Subversion 
and its working really nicely. I was wondering if you would be 
interested in this code? I have spoken to our technical director and he 
is happy for us to license it under the Apache license and donate it. I 
would also be willing to maintain the code in future if necessary. Let 
me know if you are interested.

Regards,

Adrian

Re: SvnResolver anyone?

[Xavier Hanin <xa...@gmail.com>]

On 10/22/07, Adrian Woodhead <ad...@last.fm> wrote:
>
>
> Xavier Hanin wrote:
> > Contacting people behind Ivy tools is very simple: you're talking to one
> :-)
> > If you give me your sourceforge id I can give commit rights on ivytools.
> The
> > problem is that the site is not maintained, so I don't know if it's a
> good
> > idea unless you are willing to do some work for the site too. If you
> prefer
> > to release it separately, this is a pretty good option too.
> >
> > Keep us informed anyway, and we will at least add a link to your
> resolver in
> > the Ivy links section if you host it somewhere.
> >
>
> OK, I have spoken to our technical director and we are happy to host it
> at the site where we put all the other open source code developed at
> last.fm. I will work on this over the next couple of days and will send
> a link to this list when it is ready. If you are happy with it and
> willing to link it on the Ivy site that would be great.


Great, keep us posted!

Xavier

Regards,
>
> Adrian
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/

Re: SvnResolver anyone?

[Matt Benson <gu...@yahoo.com>]

--- Adrian Woodhead <ad...@last.fm> wrote:

> 
> Matt Benson wrote:
> > While we're on this subject, I'd like to clarify: 
> is
> > it not true that a svn repo exposed over http/s
> can be
> > accessed by a url resolver?
> >   
> AFAIK it can be, but only for retrieving, not
> publishing. We need to 
> publish and also our svn repository isn't available
> over http/s, which 
> is why we had to code up our own resolver...

Good point RE publishing.  I think I had worked that
one out for myself last week but then forgot it over
the (busy) weekend.  Thanks!

-Matt

> 
> Adrian
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: SvnResolver anyone?

[Adrian Woodhead <ad...@last.fm>]

Matt Benson wrote:
> While we're on this subject, I'd like to clarify:  is
> it not true that a svn repo exposed over http/s can be
> accessed by a url resolver?
>   
AFAIK it can be, but only for retrieving, not publishing. We need to 
publish and also our svn repository isn't available over http/s, which 
is why we had to code up our own resolver...

Adrian

Re: SvnResolver anyone?

[Matt Benson <gu...@yahoo.com>]

--- Adrian Woodhead <ad...@last.fm> wrote:

> 
> Xavier Hanin wrote:
> > Contacting people behind Ivy tools is very simple:
> you're talking to one :-)
> > If you give me your sourceforge id I can give
> commit rights on ivytools. The
> > problem is that the site is not maintained, so I
> don't know if it's a good
> > idea unless you are willing to do some work for
> the site too. If you prefer
> > to release it separately, this is a pretty good
> option too.
> >
> > Keep us informed anyway, and we will at least add
> a link to your resolver in
> > the Ivy links section if you host it somewhere.
> >   
> 
> OK, I have spoken to our technical director and we
> are happy to host it 
> at the site where we put all the other open source
> code developed at 
> last.fm. I will work on this over the next couple of
> days and will send 
> a link to this list when it is ready. If you are
> happy with it and 
> willing to link it on the Ivy site that would be
> great.
> 

While we're on this subject, I'd like to clarify:  is
it not true that a svn repo exposed over http/s can be
accessed by a url resolver?

Thanks,
Matt

> Regards,
> 
> Adrian
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: SvnResolver anyone?

[Adrian Woodhead <ad...@last.fm>]

Xavier Hanin wrote:
> Contacting people behind Ivy tools is very simple: you're talking to one :-)
> If you give me your sourceforge id I can give commit rights on ivytools. The
> problem is that the site is not maintained, so I don't know if it's a good
> idea unless you are willing to do some work for the site too. If you prefer
> to release it separately, this is a pretty good option too.
>
> Keep us informed anyway, and we will at least add a link to your resolver in
> the Ivy links section if you host it somewhere.
>   

OK, I have spoken to our technical director and we are happy to host it 
at the site where we put all the other open source code developed at 
last.fm. I will work on this over the next couple of days and will send 
a link to this list when it is ready. If you are happy with it and 
willing to link it on the Ivy site that would be great.

Regards,

Adrian

Re: SvnResolver anyone?

[Xavier Hanin <xa...@gmail.com>]

On 10/16/07, Adrian Woodhead <ad...@last.fm> wrote:
>
> Thanks for your reply, Xavier, comments below:
>
> Xavier Hanin wrote:
> > It could be interesting to have one more resolver but first a question:
> do
> > you use a svn client library (like SVNKit) or the svn command line, or
> > subversion java binding? Depending on SVNKit is incompatible with the
> > allowed licenses at the ASF for instance.
> >
> I am using the SVNKit Java library. I thought from their licensing
> description that it would be compatible with ASF as their library is
> allowed to be used as long as the project using it is open source, which
> Ivy is. However, would an incompatibility arise if you shipped Ivy with
> it, in that people using it would then have to provide the code for
> their project, which isn't a requirement of the ASF license?


Yes, that's the point. Even with a more flexible license it could still be a
problem if the license is not a known and widely adopted license, there is
good chance that here at the ASF we wouldn't be able to use it.

I'm not a
> licensing expert so I'm assuming someone on this list knows more... So
> if you say this is incompatible with ASF then I guess all discussion of
> me submitting patches etc. ends here?


For inclusion in Ivy, I'm afraid so.

> Then there is the problem of maintenance... to maintain the code you need
> > commit rights, and we can't grant commit rights on the basis of only one
> > contribution. So you'd need to provide patches to maintain the code...
> > Moreover, if you finally give up on maintaining the code, we (Ivy team)
> > would have to maintain it. So we'd need to see how the code looks like,
> how
> > is it tested and documented.
> >
> Understood.
> > What I can recommend since you have the approval of your technical
> director
> > is to open a JIRA issue and attach a patch to our code base with your
> svn
> > resolver implementation. Please remember to check the box about
> transfering
> > rights to the ASF, so that we can apply the patch if we agree on that.
> Then
> > even if we do not include your patch, any user in the community would be
> > able to use it (as long as you use the ASL), so it isn't lost.
> OK, would you still want me to do this if I use SVNKit?


Let's say that even if there is no chance to get included it's the poor man
way to share your code. But using another hosting solution (see below) is a
better solution.

> Another
> > option would be to contribute it to ivytools where there is the first
> > version of a svn resolver. The problem is that ivytools is not
> maintained
> > anymore, and thus I doubt it would gain much momentum over there.
> >
> True. I could try contact the people behind ivytools and see if there is
> anyone there willing to get it going again for Ivy 2.0. Another option I
> guess would be releasing it somewhere else separately.....


Contacting people behind Ivy tools is very simple: you're talking to one :-)
If you give me your sourceforge id I can give commit rights on ivytools. The
problem is that the site is not maintained, so I don't know if it's a good
idea unless you are willing to do some work for the site too. If you prefer
to release it separately, this is a pretty good option too.

Keep us informed anyway, and we will at least add a link to your resolver in
the Ivy links section if you host it somewhere.

Xavier

Adrian
>
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/

Re: SvnResolver anyone?

[Adrian Woodhead <ad...@last.fm>]

Thanks for your reply, Xavier, comments below:

Xavier Hanin wrote:
> It could be interesting to have one more resolver but first a question: do
> you use a svn client library (like SVNKit) or the svn command line, or
> subversion java binding? Depending on SVNKit is incompatible with the
> allowed licenses at the ASF for instance.
>   
I am using the SVNKit Java library. I thought from their licensing 
description that it would be compatible with ASF as their library is 
allowed to be used as long as the project using it is open source, which 
Ivy is. However, would an incompatibility arise if you shipped Ivy with 
it, in that people using it would then have to provide the code for 
their project, which isn't a requirement of the ASF license? I'm not a 
licensing expert so I'm assuming someone on this list knows more... So 
if you say this is incompatible with ASF then I guess all discussion of 
me submitting patches etc. ends here?

> Then there is the problem of maintenance... to maintain the code you need
> commit rights, and we can't grant commit rights on the basis of only one
> contribution. So you'd need to provide patches to maintain the code...
> Moreover, if you finally give up on maintaining the code, we (Ivy team)
> would have to maintain it. So we'd need to see how the code looks like, how
> is it tested and documented.
>   
Understood.
> What I can recommend since you have the approval of your technical director
> is to open a JIRA issue and attach a patch to our code base with your svn
> resolver implementation. Please remember to check the box about transfering
> rights to the ASF, so that we can apply the patch if we agree on that. Then
> even if we do not include your patch, any user in the community would be
> able to use it (as long as you use the ASL), so it isn't lost. 
OK, would you still want me to do this if I use SVNKit?
> Another
> option would be to contribute it to ivytools where there is the first
> version of a svn resolver. The problem is that ivytools is not maintained
> anymore, and thus I doubt it would gain much momentum over there.
>   
True. I could try contact the people behind ivytools and see if there is 
anyone there willing to get it going again for Ivy 2.0. Another option I 
guess would be releasing it somewhere else separately.....

Adrian

Re: SvnResolver anyone?

[Xavier Hanin <xa...@gmail.com>]

On 10/15/07, Adrian Woodhead <ad...@last.fm> wrote:
>
> Hey there,
>
> I mailed this list a few weeks back with some questions about writing a
> custom Ivy resolver which uses Subversion to store artifacts. Well, I
> have done this using the code from your 2.0 alpha release and we are now
> using it actively to retrieve and publish files to and from Subversion
> and its working really nicely. I was wondering if you would be
> interested in this code? I have spoken to our technical director and he
> is happy for us to license it under the Apache license and donate it. I
> would also be willing to maintain the code in future if necessary. Let
> me know if you are interested.


It could be interesting to have one more resolver but first a question: do
you use a svn client library (like SVNKit) or the svn command line, or
subversion java binding? Depending on SVNKit is incompatible with the
allowed licenses at the ASF for instance.

Then there is the problem of maintenance... to maintain the code you need
commit rights, and we can't grant commit rights on the basis of only one
contribution. So you'd need to provide patches to maintain the code...
Moreover, if you finally give up on maintaining the code, we (Ivy team)
would have to maintain it. So we'd need to see how the code looks like, how
is it tested and documented.

What I can recommend since you have the approval of your technical director
is to open a JIRA issue and attach a patch to our code base with your svn
resolver implementation. Please remember to check the box about transfering
rights to the ASF, so that we can apply the patch if we agree on that. Then
even if we do not include your patch, any user in the community would be
able to use it (as long as you use the ASL), so it isn't lost. Another
option would be to contribute it to ivytools where there is the first
version of a svn resolver. The problem is that ivytools is not maintained
anymore, and thus I doubt it would gain much momentum over there.

Xavier

Regards,
>
> Adrian
>



-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/