On Apr 2, 2010, at 2:03 PM, Justin Edelson wrote:

> On Apr 2, 2010, at 1:59 PM, Kathryn Huxtable <kath...@kathrynhuxtable.org
>> wrote:
> 
>> I don't really think there's a conceptual misunderstanding on my
>> part, since the format for the CVS URL in the SCM code allows for a
>> "module_name" as part of the URL, and not in standard URL syntax.
>> 
>> But I take your point.
>> 
>> My basic question of the moment is, who calls putDirectory? Is it
>> called from the release plugin? It seems to be getting called from
>> the site plugin.
>> 
> This is a bit like asking "who calls System.out.println"; it's not
> really answerable. Wagon exposes an API and anyone is free to use it.
> I've written a few (closed source) plugins which use putDirectory and
> I suspect I'm not alone in this.

Well, yeah, but I was trying to get at the expectations. The wagon-scm thing 
adds the target to the end of the repo, which, as has been pointed out, only 
works for subversion. *I'm* not the one doing it!

> AFAIK, the release plugin does not call putDirectory. The site:deploy
> mojo does.

That was my guess.

>> The wagon documentation leaves something to be desired for the
>> unfamiliar developer. Yes, there are javadocs, but they don't tell
>> you *how* the public methods and classes are used. I'm trying to
>> figure that out without complaining too much, or looking at all the
>> code that uses wagons.
> Doesn't matter *how* they're used. The only thing that matters is the
> contract of the API. If someone uses the Wagon API incorrectly, it
> sucks to be them, but it's not really your problem. If the API
> contract needs clarification, that's a seperate issue, but I seem to
> remember the Wagon API being relatively obvious.

I think it needs a bit of clarification.

> IMHO, you should be writing your own wagon implementation and avoid
> using wagon-scm. This use case is very specific to github. This way,
> you're free to define your own URL syntax.

Well, that's what I was thinking about doing. It looks to me as if the 
wagon-scm is in pretty early stages and really only works with svn.

I'm still boggled that wagons don't seem to be configurable.

I'll take a closer look at the API javadocs. Again, I think there should be 
more site docs for wagons.

Thanks very much for your response,

-K



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to