As there is no reliable way for http client to get a list of files from a generic dumb http server, I decided against implementing getFileList(). And in the problem domain of accessing Maven repositories, that is fine, because the problem of getting a content list is solved on higher level - above transport provider, via metadata.xml.

Hope this explains my decision,
Oleg

Dan Tran wrote:
hmm, the wagon interface is generic, why do we want it to know any
thing about Maven repository like maven-metadata.xml?

-D

On Sun, Oct 12, 2008 at 12:04 PM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:
Same thing: instead of scraping html pages for the of of files - use
maven-metadata.xml to get what files are available. The big issue, as I
mentioned, is lack of any metadata for classifiers, so you'll have to
try/fail for known classifiers: sources, javadoc, etc.

Now I am curious: what's the problem you are tying to tackle with
getFileList() ?

Thanks,
Oleg

Dan Tran wrote:
We we taking about the same thing here?

what getFileList() has any thing to do with metadata or
maven-metadata.xml????


-D

On Sun, Oct 12, 2008 at 9:16 AM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:

Try using the metadata? I count only on that in Mercury repository
implementation. Plus I will provide a utility to create/correct
maven-metadata.xml files on the file system.

The only big problem is that classifiers are not covered anywhere, to
deal
with them I had to extend the metadata model, but that is not compatible
with modello-generated readers and writers. So I had to backup for now,
but
that question needs to be addressed sooner ot later.

Oleg

Dan Tran wrote:

yup, getFileList is not there, but resourceExists is there.

I use both getFileList and resourceExists to figure out a  list of
remote files recursively.
This way to plugin can base on that list and download files.  However,
i can just docs
the work around to have user to use http wagon instead.

-D

On Sun, Oct 12, 2008 at 8:50 AM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:


Correct, it did not. As well as resourceExists() - in those two I count
on
metadata.xml to exist in the remote repo. And as it was not mandated by
ITs
- I thought it's ok.

What breaks?

Oleg

Dan Tran wrote:


Oleg, the mercury dav comes with 2.1-M2-SNAPSHOT has not implemented
Wagon.getFileList yet

[ERROR] FATAL ERROR
[INFO]

------------------------------------------------------------------------
[INFO] The wagon you are using has not implemented getFileList()
[INFO]

------------------------------------------------------------------------
[INFO] Trace
java.lang.UnsupportedOperationException: The wagon you are using has
not
impleme
nted getFileList()
     at
org.apache.maven.wagon.AbstractWagon.getFileList(AbstractWagon.java:8
24)
     at
org.codehaus.mojo.wagon.WagonUtils.scanRemoteRepo(WagonUtils.java:107
)
     at
org.codehaus.mojo.wagon.WagonUtils.getFileList(WagonUtils.java:38)
     at org.codehaus.mojo.wagon.ListMojo.execute(ListMojo.java:54)
     at
org.codehaus.mojo.wagon.AbstractWagonMojo.execute(AbstractWagonMojo.j
ava:122)

On Sat, Oct 11, 2008 at 4:58 PM, Dan Tran <[EMAIL PROTECTED]> wrote:



i will try,

However, I would like to my wagon plugin to work with any wagon
extenstion.  When to plan to release the first wagon-mercury
provider?





http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/wagon/wagon-mercury
is up to date?

Thanks

-Dan


On Sat, Oct 11, 2008 at 11:28 AM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:



Dan - there are two packages there - zip, gz; try zip:




http://people.apache.org/~ogusakov/repos/staging/org/apache/maven/apache-maven/2.1.0-M2-SNAPSHOT


No - you don't have to switch protocol, mercury there is a
replacement
for
the below-mentioned protocols and passed all the ITs.

Cheers,
Oleg

Dan Tran wrote:



oleg

I can't unpack it your maven dist

-D

On Fri, Oct 10, 2008 at 9:50 PM, Dan Tran <[EMAIL PROTECTED]>
wrote:




I dont have to declare mercury in <extensions> tag right?

am I still use "dav:" for wagon url?

-D

On Fri, Oct 10, 2008 at 9:41 PM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:




Dan,

I have 2.1-M2-SNAPSHOT with Mercury wagon packaged into it for
http/https/dav, if you are interested -




http://people.apache.org/~ogusakov/repos/staging/org/apache/maven/apache-maven/2.1.0-M2-SNAPSHOT/apache-maven-2.1.0-M2-20081003.231722-1-bin.gz

Thanks,
Oleg

Dan Tran wrote:




i am using 2.1-M2, have not tested with web deployment yet.
However
my
IT test show i can download a single file using a dav url

Any how, it turns how i need both xerces adn commons-collections
in
my
extensions.

but I now run into 2 issues:

 1 getFileList from
https://dav.codehaus.org/snapshots.repository/mojo
 return "..DS_Store"

 2. getFilelist from

https://dav.codehaus.org/snapshots.repository/mojo/some/valid/path

 returns exception:

[INFO] [wagon:list {execution: list}]
[INFO] Listing
https://dav.codehaus.org/snapshots.repository/mojo
...
Oct 10, 2008 8:08:03 PM
org.apache.commons.httpclient.auth.AuthChallengeProcesso
r selectAuthScheme
INFO: basic authentication scheme selected
[INFO]




------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]




------------------------------------------------------------------------
[INFO] Error handling resource

Embedded error: Destination path exists but is not a WebDAV
collection
(director
y):




https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT


so it seems we cannot use full path to dav's URL

is this a bug in wagon webdav?

-D

On Fri, Oct 10, 2008 at 7:56 PM, Brett Porter
<[EMAIL PROTECTED]>
wrote:





It will need to be added to the extensions.

It really shouldn't be necessary though - what version of Maven
are
you using, and does the dav deployment work normally?

- Brett

2008/10/11 Dan Tran <[EMAIL PROTECTED]>:





Ok, i added         xerces to my plugin's classpath, still no
go.


still looking

-D


On Fri, Oct 10, 2008 at 7:45 PM, Brett Porter
<[EMAIL PROTECTED]>
wrote:





No, I think you need to add xerces, or find out why the
jackrabbit
version of those classes are being used instead of the
patched
version
(there's also a chance that there is a new release of
jackrabbit
that
includes the patch now - I haven't checked).

- Brett

2008/10/11 Dan Tran <[EMAIL PROTECTED]>:





No sure how to proceed.

are you suggesting me to add jackrabt to my plugin;'s
classpath?

-D

On Fri, Oct 10, 2008 at 7:23 PM, Brett Porter
<[EMAIL PROTECTED]>
wrote:





2008/10/11 Dan Tran <[EMAIL PROTECTED]>:





Hello,

I am currently continue on with James Dumay's
wagon-maven-plugin
at
MOJO's sanbox and running to issue invokes'
Wagon:getFilelist()
with
wagon-webdav-jackrabbit

The IT pom is at





http://svn.codehaus.org/mojo/trunk/sandbox/wagon-maven-plugin/src/it/webdav






Maybe this is a classpath ordering problem - to apply a
patch
from
Jackrabbit's JIRA we included a couple of Jackrabbit source
files
in
the wagon. If the versions from Jackrabbit are being used
instead
it
is fine, but you will need to include Xerces as a
dependency
as
well.






I also try it with with wagon-webdav-beta-2, the
getFilelist
returns
wrong data.





Yep, that bug was fixed up in beta-4.

- Brett
--
Brett Porter
Blog: http://blogs.exist.com/bporter/





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--
Brett Porter
Blog: http://blogs.exist.com/bporter/





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--
Brett Porter
Blog: http://blogs.exist.com/bporter/




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to