the deeplink used to work: that's the objective of our "resources/download.cgi + xdoc/download.xml.vm" pattern that was created some years ago. download.cgi is supposed to use standard ASF script that uses download.html as content
I don't know why this does not work any more. I vaguely remember something a few years ago about executable bit, some headache I had at that time to try to fix working with interested people (ie. not many, but Sebb was probably one of the few). Perhaps it's time to rework on it: I'll see tonight if I can find references on the analysis already done at that time. Regards, Hervé Le vendredi 17 novembre 2017, 12:27:49 CET Robert Scholte a écrit : > This topic deserves a separate mailthread. > > Quoting Sebb on a different thread: > "The download link points to the top-level of the ASF mirror system. > > This makes it very hard to use." > > AFAIK the ASF says there should be a download button for every released > product. > In case of Maven we're talking about a lot of projects, and downloads > should be redirected via a mirror. > I don't think it is possible to do a deeplink to a specific folder. > > Also, in case of Maven plugins and other dependencies (all excluding the > Maven distribution itself) it is kind of strange to provide a download > link when we could assume that they only want to have the > plugin/dependency XML fragment. > > I agree that the link is kind of useless right now, but also the best we > can do when providing a direct download link. > If there's no way to do a deeplink, I'd prefer to remove it from the pages > and announcements. > > thanks, > Robert > > --------------------------------------------------------------------- > 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]
