I just reopenned it.
Seems there was confusion between ProxyRequestHandler and ProxiedDavServer.
Having to handle snapshots requires to bypass any optimisation of searching
for existing artifacts. Maybe we could detect the request to point to an
artifact (or meta-datas) ? Or maybe this should be d
I closed it because the points raised were in areas / objects / classes
that I felt no longer existed in the current codebase.
I COULD BE WRONG! (quite likely actually)
Feel free to reopen any ticket you feel needs more attention.
Don't be afraid to reopen tickets, especially with an explanat
Why is this no longer valid ?
When I ask for a snapshot that is allready present in the managed repo, the
proxied repository are not fetched as the "hasRessource" return true...
I'll prepare a testCase for snapshots updates and attach it to jira, so it
can be better tested.
2007/8/7, Joakim Erdfe
I'm the one that closed that jira.
I only closed it as won't fix because there wasn't an option "no longer
valid". ;-)
The CacheFailurePolicy catch was good, thanks! it'll be fixed in svn
shortly.
If I could trouble you to report any snapshot bugs you find into jira
(that would be wonderful)
Noted. I'll look into that wrapper problem.. Thanks!
-Deng
nicolas de loof wrote:
MRM-460 created.
The typo is only in CacheFailurePolicy log message.
The main issue is about the archiva default config that refers to an invalid
"cache" value.
Abnother issue with the proposed beta : I had to e
+1
The licenses and signatures are all in place, and it appears to be
running fine.
I tested the plexus-runtime version and it deleted 2/3 of my
repository - just like I asked it to :)
Cheers,
Brett
On 07/08/2007, at 2:23 AM, Maria Odea Ching wrote:
Hi All,
Archiva 1.0-beta-1 is now r
