I tried the same maven1 request on an from-scratch archiva instance running in plexus (my corporate archiva runs on tomcat5). Same 404 error for legacy requests.
I also still have the wrapper.conf issue I noticed on beta 2 for windows : [ERROR] Specified initial heap size (3 MB) is less than the minimum required initial heap size (8 MB). changing wrapper.java.initmemory=8 in wrapper.conf solves this. 2007/10/23, nicolas de loof <[EMAIL PROTECTED]>: > > Sorry to come late on this thread. > > I made some test as a maven1 client and can't get any content from the > repository : > > > http://localhost:8080/archiva/repository/internal/javax/servlet/servlet-api/2.3/servlet-api-2.3.jarreturns > the expected jar > > > http://localhost:8080/archiva/repository/internal/javax.servlet/jars/servlet-api-2.3.jar > returns 404. > > Something is broken in this release... > > > Other m1 request that was not resolved in beta2 are now well downloaded, > but also fails in 404. It seems ANY legacy request fails. > > Nico. > > > 2007/10/23, Brett Porter <[EMAIL PROTECTED]>: > > > > > > On 23/10/2007, at 11:06 AM, Joakim Erdfelt wrote: > > > > > > > > I get a "Configuration can not be saved when it is loaded from two > > > sources" error when I use this standalone build. > > > I can't get any of the admin screens to work. > > > > > > Works OK if I use the war file on tomcat tho. (Wow! what a > > > difference from a month ago) > > > > As detailed in the other mail, not a release blocker, and no > > different to the behaviour in the last release. > > > > - Brett > > > > -- > > Brett Porter - [EMAIL PROTECTED] > > Blog: http://www.devzuz.org/blogs/bporter/ > > > >
