I allready noticed this no-update-check issue on 0.9 in MRM-320, but maybe I wasn't clear as it was closed as "won't fix".
I'm looking for a clean way to pre-process the DAV request before proxies connectors get fetched. This could include the legacy -> default (or any other) request path layout conversion. For now, the only way I've found is to add some code in ProxiedDavServer. Could ArtifactReference, VersionedReference and ProjectReference share an ancestor so that we can refactor BidirectionalRepositoryLayout to only provide toReference(path) and toPath(Reference) ? This would avoid having similar try/catch 3 times. 2007/6/5, Joakim Erdfelt <[EMAIL PROTECTED]>:
MRM-412 will make it into Archiva 1.0-alpha-2 thanks! As for the check for the requested file issue, yes that is a mistake, likely left over from an earlier time, when things were more chaotic, a time when great herds of horned alpacas roamed the earth. - Joakim nicolas de loof wrote: > I just submitted MRM-412 and attached a patch. > > This issue adds support for any layout to the DavServlet : > Requesting "/javax.servlet/jars/servlet-api-2.3.jar" or > "/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar" will auto-detect the > layout used for the request (based on configured layouts in archiva) > and use > it to build the ArchivaArtifact object. > This requires the BidirectionalRepositoryLayout interface to be > enhanced to > add detection of valid path. > > please review. > > > I also notice the ProxiedDavServer does check for the requested file to > exist in managed repo before trying to proxy it. Doesn't this bypass any > update strategy configured in proxies ? Perhaps I missed something ? > > > 2007/6/4, Joakim Erdfelt <[EMAIL PROTECTED]>: >> >> doh! *I* never voted on this. :-) >> >> +1 to release. >> >> - Joakim >> >> Joakim Erdfelt wrote: >> > Archiva 1.0-alpha-1 was tagged and built this afternoon. >> > >> > The proposed distribution, including binary distributions, and >> > signatures can be found here: >> > >> > http://people.apache.org/builds/maven/archiva/1.0-alpha-1/ >> > >> > To keep up with the trend started by Wendy Smoak (sorta): >> > The 1.0-alpha-1 staged copy was setup and configured to point to >> > a pre-built repository, and then used to build the next archiva >> > snapshot (1.0-alpha-2-SNAPSHOT) in archiva/trunk. >> > >> > This will be Archiva's first release with a proper database, and >> > is intended to get a testable baseline of the archiva feature set >> > into the hands of all interested individuals. >> > >> > The list of issues identified and closed with this release can >> > be found below: >> > >> > Archiva 1.0-alpha-1 Release Notes: >> > >> > >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10980&styleName=Html&version=13443 >> >> > >> > >> > This is an alpha release, and as such, has bugs. >> > >> > Once people have a chance to kick the prototype tires, and look >> around, >> > the most urgent jira tickets will be addressed quickly for a >> 1.0-alpha-2 >> > release, with an expected release 1 to 2 weeks after this one. >> > >> > Known issues include documentation, problems with proxying, problems >> > running the webapp on Tomcat, missing reporting, empty or inaccurate >> > dependency tree information, and poor grammar. >> > These and other issues can be tracked at the URL below: >> > >> > Archiva 1.0-alpha-2 Open Issues: >> > >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10980&fixfor=13518 >> >> > >> > >> > Once you have had a chance to examine the distribution, please cast >> > your vote. We welcome votes and feedback from all community members. >> > >> > [ ] +1 Release it! >> > [ ] 0 >> > [ ] -1 Don't release it, because... >> > >> > 72 hours ends Monday afternoon (GMT -5) >> > If you need more time, just ask. >> > >> >> >> -- >> - Joakim Erdfelt >> Committer and PMC Member, Apache Maven >> Archiva Developer >> [EMAIL PROTECTED] >> [EMAIL PROTECTED] >> Alpaca Founding Member
