Since I'm working on Archiva, I've always been testing it on Tomcat 5.5.23and I've never had a single problem (using the tips provided on the Wiki: http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat)
I'll look at MRM-323 when I have some time (that is after my coming holidays :-)) Fabrice. On 8/2/07, Brett Porter <[EMAIL PROTECTED]> wrote: > > I'd be happy to run some tests on Tomcat post beta-1 as well. I've > spent way too much time battling these things in a past life not to > have learned something that might be helpful :) > > Anyone here deploying to something other than Tomcat? We have Jetty5 > (via appserver) and 6 (via plugin) covered - I'm interested to know > if these issues are isolated to TC. > > - Brett > > On 02/08/2007, at 10:32 AM, Maria Odea Ching wrote: > > > Yep, we also expect users to deploy Archiva standalone in > > production. So far, MRM-323 and all the other remaining Tomcat > > issues are scheduled for 1.0.x since most of them needs to be > > investigated further. I've looked at MRM-323 in jira and saw your > > findings for this issue. I'll take a look at it later on and > > "maybe" we could include this in beta-2 :) > > > > > > Thanks, > > Deng > > > > > > Ludovic Maitre wrote: > >> Hi Maria, all, > >> > >> Although i'm a new user of Archiva, i would like to know when in > >> the roadmap the team plan to fix issues related to running Archiva > >> inside Tomcat (issues like http://jira.codehaus.org/browse/ > >> MRM-323 ) ? Is it something important for the team ? Did you > >> expect users to deploy Archiva standalone in production ? > >> Best regards, > >> > >> Maria Odea Ching wrote: > >>> Hi All, > >>> > >>> We (Brett, Joakim and I) have segregated the issues in Jira to > >>> prep for the upcoming 1.0 release (finally! :-) ). Anyway, > >>> there'll be two beta releases first before 1.0. > >>> > >>> So..here's the plan (excerpted from Brett): > >>> - finish all issues for 1.0-beta-1 > >>> - then move on to 1.0-beta-2 issues for the next release > >>> - do a big bug bash to find the problems in it > >>> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues) > >>> > >>> > >>> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be > >>> Monday my time), and this will include the following: > >>> 1. Resolved/Closed: > >>> - MRM-290 (Ability to pre-configure the Jetty port in conf/ > >>> plexus.xml) > >>> - MRM-326 (Adding/Editing repositories doesn't have validation) > >>> - MRM-425 (Search and Browse do not work for snapshots) > >>> - MRM-426 (Search does not work for snapshots because of > >>> different version values in index and database when the snapshot > >>> version is unique) > >>> > >>> 2. In Progress/Open: > >>> - MRM-143 (Improve error reporting on corrupt jars, poms, etc) > >>> - MRM-275 (add "remove old snapshots" Scheduler) > >>> - MRM-294 (Repository purge feature for snapshots) > >>> - MRM-329 (The Reports link gives an HTTP 500) > >>> - MRM-347 (Undefined ${appserver.home} and ${appserver.base}) > >>> - MRM-373 (Unable to delete the pre-configured example network > >>> proxy) > >>> - MRM-412 (Add support for maven 1 (legacy) request to access a > >>> maven2 (default layout) repo ) > >>> - MRM-428 (Managed and remote repositories with same name causes > >>> problems) > >>> - MRM-429 (Find artifact does not work when the applet is disabled) > >>> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml) > >>> > >>> Everyone okay with this? :) > >>> > >>> > >>> Thanks, > >>> Deng > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >> > >> >
