MRM-565 created. As this makes archiva totaly unusable to maven1 users, I consider this as blocker, but maven2-only users will never get this issue, and this is only a beta-release. Based on this "release often" principle wins.
I've no idea how many archiva users use it as maven1 proxy. In my case archiva is used as a coporate proxy, and maven1 support is required for legacy projects (and there is many !). The release note should warn on this. Nico. 2007/10/23, Brett Porter <[EMAIL PROTECTED]>: > > *sigh*. Confirmed. > > I can see exactly where it is broken too. The resourceExists is using > what appears to be the request path to look in the managed repository > which is of a different layout. The error message is also wrong, > leaving out the repository ID. > > I'm going to be bold and say this can wait until beta-4 and should be > listed as a known issue in the release notes. I'd like to get the > current release in the hands of the m2 users and progress to beta-4 > early next week. What do others think? Nicolas, in particular, are > you happy with that or do you feel we should not release it? > > Can you make sure this is in JIRA in the mean time? > > Cheers, > Brett > > On 23/10/2007, at 6:36 PM, nicolas de loof wrote: > > > 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/ > >> > > -- > Brett Porter - [EMAIL PROTECTED] > Blog: http://www.devzuz.org/blogs/bporter/ >
