Hi, I have the same problem. I tried to upgrade from 2.6.7 to 3.0.2 (professional license). We have several in house repositories with hundreds of GB of artifacts and some cached external repos with a lot of artifacts.
The System export did work well, and after the import was finished successfully (some errors occurred, mostly metadata specific) a some in house repositories and the caches of the external repositories have been here but not our two most important repositories for our releases. They are configured, yes but they are completely empty. Before we used a H2 DB and now we wanted to use the default (derby db) Has anyone else this problem? Does anyone know what the problem is? kind regards Volker -- View this message in context: http://forums.jfrog.org/Upgrade-to-Artifactory-3-x-empty-repository-tp7578964p7578987.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
