In fact we are not 'packaging' it, but we 'distribute' it via download links. 
So from the de iure point this is really edgy. 

The easiest thing would be to simply ask svnkit folks to give us a consensus 
letter that we are allowed to use it for maven-scm or even better a general 
clearance for using it in Apache projects.

LieGrue,
strub

--- Jason van Zyl <jvan...@sonatype.com> schrieb am Do, 19.3.2009:

> Von: Jason van Zyl <jvan...@sonatype.com>
> Betreff: Re: svnjava provider and maven scm
> An: scm-dev@maven.apache.org
> Datum: Donnerstag, 19. März 2009, 9:29
> On 19-Mar-09, at 1:25 AM, Olivier
> Lamy wrote:
> 
> > Hi,
> > Ok. It's was not really clear for me.
> > 
> 
> Technically we are not redistributing anything and we can
> ask the board for clarification because in the strictest
> sense we do not redistribute. But I think folks here would
> interpret a dependency in your POM as being equivalent.
> 
> > Thanks for clarification,
> > --
> > Olivier
> > 
> > 2009/3/19 Jason van Zyl <jvan...@sonatype.com>:
> >> If the license is not one that the ASF accepts
> then we can't really dodge
> >> the issue by saying that it's only in the POM.
> >> 
> >> On 18-Mar-09, at 5:22 PM, Olivier Lamy wrote:
> >> 
> >>> Hi,
> >>> As we don't distribute the svnkit (it's only a
> dependency available in
> >>> the central repo), why we can't make a release
> of this provider ?
> >>> Any objections to move the sandbox module in
> trunk ?
> >>> 
> >>> Thanks,
> >>> --
> >>> Olivier
> >> 
> >> Thanks,
> >> 
> >> Jason
> >> 
> >>
> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder,  Apache Maven
> >> http://twitter.com/jvanzyl
> >>
> ----------------------------------------------------------
> >> 
> >> To do two things at once is to do neither.
> >> 
> >>  -—Publilius Syrus, Roman slave, first
> century B.C.
> >> 
> >> 
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
> 
> 
> 



Reply via email to