Re: [vote] Release Archiva 1.0

+1 Release it! - Joakim Maria Odea Ching wrote: Hi Everyone, The Archiva 1.0 release candidate has been prepared. Regressions for m1 proxy requests found in 1.0-beta-4 have been fixed and the important documents for the site have been completed. You can take a look at the release notes for Ar

Re: [vote] Release Archiva 1.0

+1! The source builds with tests skipped, as I found one problem otherwise - the source build fails with a test error in the repository layer that doesn't happen on trunk - I don't think this is a blocker and probably just needs an extra note in the release notes and investigate later why

Re: [vote] Release Archiva 1.0

[X] +0 "Let's release it, even if I'd expect some more fixes !" Not voting 0 or -1 as some stable archiva release is expected for too long, but archiva CANNOT be used with legacy maven1 projects as it cannot serve jaxen-1.0-FCS-full, that is used by some maven1 core plugins Applying my MRM-594 fi

[vote] Release Archiva 1.0

Hi Everyone, The Archiva 1.0 release candidate has been prepared. Regressions for m1 proxy requests found in 1.0-beta-4 have been fixed and the important documents for the site have been completed. You can take a look at the release notes for Archiva 1.0 here: http://jira.codehaus.org/secure/Rel

[Results] [VOTE] Release Archiva-1.0-beta-3 (Take 2)

Below are the results of this vote: +5 Binding Votes (Fabrice, Joakim, Brett, John T. and Myself) +1 Non-binding Votes (James) I'll finalize the release and will send an update. Thanks, Deng On 10/30/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote: > > Hi Everyone, > > Take 2.. :) > > Archiva

Re: [RESULTS] [VOTE] Release Archiva 1.0-beta-3 (Postpone the release)

I can do another release at the end of this week :) Everybody okay with that? -Deng Brett Porter wrote: I've merged 1.0-beta-4 back into 1.0-beta-3 in JIRA too. When would you like to cut the release again Deng? The only pre-condition I see is that we do need another plexus-webdav release f

Re: [RESULTS] [VOTE] Release Archiva 1.0-beta-3 (Postpone the release)

I've merged 1.0-beta-4 back into 1.0-beta-3 in JIRA too. When would you like to cut the release again Deng? The only pre-condition I see is that we do need another plexus-webdav release first now - are all the webdav related JIRAs closed now Joakim? Cheers, Brett On 26/10/2007, at 4:41 PM,

Re: [VOTE] Release Archiva 1.0-beta-3

I opened MRM-561 (non-blocking) logs seems to be in DEBUG by default :-( and when I start it I have it saying "welcome you to maven Archiva Unknown", instead to have 1.0-beta-3 Otherwise it seems to work fine (tested only with maven 2). +1 On 22/10/2007, Brett Porter <[EMAIL PROTECTED] > wrote:

Re: [VOTE] Release Archiva-1.0-beta-1

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

Re: [VOTE] Release Archiva-1.0-beta-1

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

Re: [VOTE] Release Archiva-1.0-beta-1

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

Re: [VOTE] Release Archiva-1.0-beta-1

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)

Re: [VOTE] Release Archiva-1.0-beta-1

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

Re: [VOTE] Release Archiva-1.0-beta-1

+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

[RESULTS] [VOTE] Release Archiva 1.0-alpha-1

The following are the results of this vote. +5 Binding Votes ( Jesse, Emmanuel, Wendy, Fabrice, and Myself) +2 Non-binding Votes (Maria, and Nicolas) The release is good to go. I'll send another update when it has been completed. - Joakim Joakim Erdfelt wrote: Archiva 1.0-alpha-1 was tagged a

Re: [VOTE] Release Archiva 1.0-alpha-1

I agrea. Simply adding support for converting legacy -> default requests requires to patch the DavServer. Adding support for server-side relocation requires even more. A new layer between Dav servlet and the repository (and it's proxies) would make things cleaner and extensible. Is there any draf

Re: [VOTE] Release Archiva 1.0-alpha-1

I don't like hooking up the webdav interface into the dynamic artifact serving. I think we need to investigate the DASL layer idea in the Archiva Roadmap, maybe move it up in priority. http://docs.codehaus.org/display/MAVENUSER/Archiva+Roadmap - Joakim nicolas de loof wrote: I allready notice