Sorry!
I have just checked out the entire trunk and now I don't get compilation
errors on those classes.
zsolt
>-Original Message-
>From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
>Sent: Saturday, April 08, 2006 7:19 PM
>To: scm-users@maven.apache.org
>Subject: Re: Where is org.apache.m
hehe, the command must be read 'mvn clean install' in
maven-scm-provider-svn-commons directory
Emmanuel
Zsolt a écrit :
I got:
mvn clean install in maven-scm-provider-svn-commons
[INFO] Scanning for projects...
[INFO]
Zsolt wrote:
I got:
mvn clean install in maven-scm-provider-svn-commons
You typed "mvn in" somewhere in there.
[INFO] Scanning for projects...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
---
I got:
mvn clean install in maven-scm-provider-svn-commons
[INFO] Scanning for projects...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Invalid task 'in
I completely agree. The best way would be as Torbjorn wrote:
"Being able to add a spesific command without expanding the ScmProvider
would have been great."
The core of scm-maven should remain compact and easy to maintain, but
unfortunately right now, I think the only way is to add the commands I
Trygve,
I'm not sure whether you also red discussions last week.
You are right: list-files can be solved with checkout. But lets take a huge
project (for example 10.000) files. You want to see the list of the files in
the top directory only. I estimate you don't want to checkout the entire
reposi
If our aim is to support a superset of all SCM commands, then this
Task system should definitivly be supported. But we should perhapes
think about distinguis core SCM commands (commands that virtually all
SCM supports) and provider spesific commands.
Being able to add a spesific command without exp
On Fri, 2006-04-07 at 19:34 +0200, Zsolt Koppany wrote:
> Hi,
>
> this mailing list doesn't allow attachments, thus I have just pasted the
> source code.
>
> It doesn't contain any implementation but the methods are really necessary
> for me.
>
> I extended ScmProvider but actually I think, the
