Are you sure that CONTINUUM-2013 is really fixed? I am trying to migrate from Continuum 1.2.3 to 1.3.6. Exporting the data with the migration tool 1.2.3.1 worked fine after manually downloading some jars and installing them using maven install. I got a nearly 9MB builds.xml then ... However, when trying to import these data in Continuum 1.3.6 with the migration tool 1.3.6, I encountered lots of ClassNotFoundExceptions for those classes that have been given plexus annotations in the patch attached here. How can I solve that problem?
Thanks, Manfred Wendy Smoak-3 wrote: > > ... > However, since as of 1.3.0 we had no way to upgrade and that blocked > the release, I'll take what I can get. :) > ... >> My only concerns is to have a migration tool working for 1.2.x to 1.3.1 >> ?? >> Are you sure this doesn't need any manual update in the database ?? > >>> I applied the patch submitted by Jan Ancajas for CONTINUUM-2013 (1.2.x >>> to >>> 1.3.x db migration tool). The main problem with the migration tool in >>> trunk >>> are the component lookup errors because the continuum-store module has >>> already been converted to spring annotations. The fix to get the tool >>> working requires plexus annotations to be added back to continuum-store. >>> I >>> already applied the fix in trunk -r735074 since we need the tool to >>> get a *1.3.1 >>> alpha* release out and we could just port the migration tool to Spring >>> in >>> the succeeding 1.3.x releases.. > -- View this message in context: http://old.nabble.com/CONTINUUM-2013-tp21505445p29423646.html Sent from the Continuum - Dev mailing list archive at Nabble.com.
