I am inclined to agree, having wrestled with this all day. On Tue, Jul 5, 2011 at 9:10 PM, Brett Porter <[email protected]> wrote: > > On 06/07/2011, at 4:25 AM, Benson Margulies wrote: > >> I'm posting this thread, even though I can pretty much guarantee that >> I'm not going to be able to muster the effort to act on it. >> >> Sitting over at mojo is a wagon-maven-plugin. It wants to enumerate >> all the artifacts in a repo. It tries to do this by walking the repo >> as a directory tree. >> >> Sadly for it, the wagon protocol is really not sufficient. I think. >> >> If you ask a wagon to list the contents at a path, it lists >> *anything*, whether it has anything to do with maven or not. It does >> not look at any metadata. > > Well, that's intentional - it doesn't have any Maven or repo smarts. > >> >> The mojo tries to deal with all this by assuming that a URL ending >> with "/" will only succeed through 'resourceExists' if it is, indeed, >> a directory. Not a good assumption, as it turns out. >> >> To make this all really work, it seems to me that either the wagons >> have to have a concept of 'directory', or they need to be stricter in >> filtering returned information. >> >> Or I'm confused, or we don't care. > > It sounds like the mojo is trying to over-stretch what Wagon itself wants to > do. Enumerating artifacts in the repo would be better done with a repo > manager or the index - it's not something a mojo wants to do "live" for a > non-trivial repo. > > - Brett > > -- > Brett Porter > [email protected] > http://brettporter.wordpress.com/ > http://au.linkedin.com/in/brettporter > > > > > > --------------------------------------------------------------------- > 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]
