tch to svnkit as a default implementation not to
put it on repo.apache.org.
LieGrue,
strub
[1] http://svnkit.com/licensing.html
--- Olivier Lamy schrieb am Mi, 1.7.2009:
> Von: Olivier Lamy
> Betreff: Re: svn commit: r784555 -
> /maven/components/branches/maven-2.1.x/maven-core/pom.x
Hi,
I think the only committer will have a look at this :-)
But the main issue will be to have the svnkit version available in central repo.
Thanks,
--
Olivier
2009/7/1 Brett Porter :
>
> On 01/07/2009, at 4:53 AM, Benjamin Bentmann wrote:
>
>> Brett Porter wrote:
>>
>>> [INFO] Cannot get the rev
On 01/07/2009, at 4:53 AM, Benjamin Bentmann wrote:
Brett Porter wrote:
[INFO] Cannot get the revision information from the scm repository :
Exception while executing SCM command.
svn: '/Users/brett/scm/maven/maven-2.1.x/maven-core' is not a
working copy
OK, as the javasvn provider seems
Brett Porter wrote:
[INFO] Cannot get the revision information from the scm repository :
Exception while executing SCM command.
svn: '/Users/brett/scm/maven/maven-2.1.x/maven-core' is not a working copy
OK, as the javasvn provider seems not to work as reliable as the regular
svn provider, I
On 30/06/2009, at 5:45 AM, Benjamin Bentmann wrote:
Hi Brett,
Unfortunately this broke the build on my machine (maybe because of a
difference in working copy version?).
Hm, can you provide some more details on the failure? I only tested
with WinXP and Ubuntu and don't have a Mac at hand,
Hi Brett,
Unfortunately this broke the build on my machine (maybe because of a
difference in working copy version?).
Hm, can you provide some more details on the failure? I only tested with
WinXP and Ubuntu and don't have a Mac at hand, so can't reproduce
easily. No idea whether I just misco
Hi Benjamin,
Unfortunately this broke the build on my machine (maybe because of a
difference in working copy version?).
Also, it doesn't appear to have been merged to the other branches.
I think perhaps we should change the activation so that this is only
included on release, or if requested (say
