I'll look at the logs but I didn't see any errors before, but it's late and I may just not remember.
I hoped I could somehow bring up a clean 1.4-M2 on the same machine (different tomcat instance/port) using the same repositories. If that is possible without causing issues with 1.3.5, then I can spend a bit more time digging into it since other users will still be functional and my release versions won't get out of whack. On Tue, Apr 17, 2012 at 11:46 PM, Deng Ching <[email protected]> wrote: > Hi Jeff, > > We're no longer using the Archiva database in 1.4+, only the users database > has been retained. The data are stored as metadata in the filesystem (by > default) for 1.4+. I read your other email in the users list regarding the > 500 error you were getting in your build. There weren't any errors at all > in the Archiva logs? What about during startup, maybe there was an error > there? > > Thanks, > Deng > > On Wed, Apr 18, 2012 at 12:59 PM, Jeff <[email protected]> wrote: > > > I tried upgrading to 1.4-M2 but had a lot of 500 Internal Server errors > > resolving dependencies and was wondering if it would hurt if I installed > > 1.4-M2 fresh in a different Tomcat container but pointed it to the same > > database server. Would that cause issues? > > > > -- > > Jeff Vincent > > [email protected] > > See my LinkedIn profile at: > > http://www.linkedin.com/in/rjeffreyvincent > > I ♥ DropBox <http://db.tt/9O6LfBX> !! > > > -- Jeff Vincent [email protected] See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox <http://db.tt/9O6LfBX> !!
