You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by Maria Odea Ching <oc...@apache.org> on 2009/01/16 19:16:42 UTC

CONTINUUM-2013

Hi All,

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..

Any thoughts or comments on this?

Thanks,
Deng

-- 
Maria Odea Ching
Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
www.exist.com | Innovation Delivered

Re: CONTINUUM-2013

Posted by "Manfred A." <ma...@hamburg.de>.
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.


Re: CONTINUUM-2013

Posted by Wendy Smoak <ws...@gmail.com>.
I'm going to try it with a large data set after lunch and update the
docs, but my bet is that it _will_ still need manual work in the
database.

There was always a problem with it not getting the next key value
correct after importing, and depending on the model changes sometimes
you needed to run it through an xslt before importing.

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. :)

-- 
Wendy

On Fri, Jan 16, 2009 at 11:31 AM, Olivier Lamy <ol...@apache.org> wrote:
> Not really.
> 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 ??
>
> --
> Olivier
>
> PS : sorry I didn't have yet the time to test this. I will try to try :-)
>
> 2009/1/16 Maria Odea Ching <oc...@apache.org>:
>> Hi All,
>>
>> 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..
>>
>> Any thoughts or comments on this?
>>
>> Thanks,
>> Deng
>>
>> --
>> Maria Odea Ching
>> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
>> www.exist.com | Innovation Delivered
>>
>

Re: CONTINUUM-2013

Posted by Olivier Lamy <ol...@apache.org>.
Not really.
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 ??

--
Olivier

PS : sorry I didn't have yet the time to test this. I will try to try :-)

2009/1/16 Maria Odea Ching <oc...@apache.org>:
> Hi All,
>
> 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..
>
> Any thoughts or comments on this?
>
> Thanks,
> Deng
>
> --
> Maria Odea Ching
> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> www.exist.com | Innovation Delivered
>