2008/8/21 EJ Ciramella <[EMAIL PROTECTED]>: > What I mean is, I could always deploy to a standalone archiva set up, it > didn't respect groups/roles/etc. I could only get archiva to respect > this when it was deployed to tomcat. Does this make sense?
The question makes sense, but I'm not familiar with the problem. > > I'd prefer to run in standalone mode (for ease of setup/etc), is there > any reason to deploy to tomcat? Not if you are happy with the Jetty set up. (the main reason would be you want to/already run tomcat for some other reason) - Brett > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 19, 2008 10:35 PM > To: [email protected] > Subject: Re: used to have to deploy to tomcat to utilize users/roles/etc > > I'm not sure what you are referring to - in what scenario was there no > users/roles under 1.0.2? > > Tomcat/other servlet containers has always been an option for > deployment, which is completely up to you. I think the default > installation (which is just the webapp pre-configured on Jetty 6, with > JSW to run it) should be a good choice for most people. > > Cheers, > Brett > > 2008/8/20 EJ Ciramella <[EMAIL PROTECTED]>: >> Hello again everyone - I noticed that deploying a 1.1.1 version of >> archiva, now in standalone mode, I have users/roles that are working. >> >> >> >> Prior to this release, in version 1.0.2, you HAD to deploy archiva to >> tomcat to get this functionality. >> >> >> >> When did this change (and how is this called out in the release > notes)? >> >> >> >> Is there any reason to use tomcat now? >> >> > > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > -- Brett Porter Blog: http://blogs.exist.com/bporter/
