On 06/11/2007, Julien CARSIQUE <[EMAIL PROTECTED]> wrote: > Hi, > > Trying to upgrade from beta-1 to beta-2, I have had some configuration > issues; more than simply change the <repositories> tag to > <managedRepositories> and <remoteRepositories>.
Archiva should have done this for you automatically - if you are planning to upgrade from beta-1 to beta-3 and have problems, let us know. BTW, Archiva has it's own list for these types of issues now if you'd like to subscribe. > What do you think I have to do for upgrading from beta-1 to beta-3 ? I posted a little bit to this list about it yesterday in another thread - but it should just work. > Which changes are expected in conf/archiva.xml ? Is there some > deprecated tags ? > And in other configuration files ? No other changes. > > Do you still not have a schema to validate it ? I can generate one for you to try - but it's not used by the application to validate it. > > I also had another issue with beta-1 : we have snapshots from trunk and > branch and wanted old snapshots to be automatically deleted but branch's > snapshots were systematically deleted during deployment because of > trunk's snapshots which were considered by archiva as more recent. What > do you think about this ? This is a known issue: MRM-576. Good luck! Thanks, Brett -- Brett Porter Blog: http://www.devzuz.org/blogs/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
