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 expanding the ScmProvider
would have been great.

An other thing... should we try to follow subversion naming? If we are
going to add a list/inventory/listFiles command, I think we should use
list (as in subversion list).

And again, when adding a new concept, it is very, very important to
include good javadoc.
What is a Task? What makes it different from a TODO listing? Whats a
typical return value from these fields. How should it be used? What
providers are likly to support it?


On 4/8/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
> 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 new methods should be added
> > to it.
> >
> > Please make you proposals.
> I don't really understand what this code is supposed to do? It seems to
> be something like a parser for TODO stuff which really isn't something
> that belongs in a SCM library.
> If what you want to do is to read out all the TODOs etc you can do that
> with a checkout/export and run a Maven report.
> --
> Trygve

Reply via email to