Something that needs to enumerate a repo should look towards leveraging the index instead of the index listing that wagon uses. Once upon a time, the wagon couldn't work with the listings of certain repo managers because they didn't render an index.html (i don't know if that's still true or not) but it's an example of using the wrong approach to get the info. It made sense pre-repo managers but today less so.
On Tue, Jul 5, 2011 at 9:25 PM, Benson Margulies <[email protected]> wrote: > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
