I did understand that, but the in-place security.xml solution, in either variant, really (*really*) didn't work for me. I'm not complaining at all, because the upgrade was no trouble and I should have done it anyway,
Noam Y. Tenne wrote: > > Glad to hear, though when performing this procedure on Artifactory > versions > 2.0.6-2.8.0, the bootstrapping file should be named *security.xml *and not > * > security.import.xml*. > > On Thu, Aug 19, 2010 at 11:16 AM, mauricen > <[email protected]>wrote: > >> >> Thanks very much. Just to let you know, I couldn't make it work without >> upgrading. Once I'd upgraded, the security.import.xml procedure worked >> fine. > -- View this message in context: http://forums.jfrog.org/Lost-admin-password-tp5435810p5439486.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
