You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cayenne.apache.org by Mike Kienenberger <mk...@gmail.com> on 2013/09/20 16:47:31 UTC

Upgrading from 3.0

So I'm looking at upgrading from 3.0.2 to 3.1 or 3.2.

I can already see that there's a lot of Configuration-related changes
I am going to have to make.

Is it easier to upgrade to 3.1 then 3.2, or from 3.0.2 to 3.2 directly?

The 3.2M1 package does not contain upgrade notes for 3.2, but only up
through 3.1.

Re: Upgrading from 3.0

Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 21/09/13 12:52am, Mike Kienenberger wrote:
> Never mind.   After reading the news posting on the 3.2 release, I see
> that it builds on 3.1, so I'm better off upgrading to 3.1 first and
> getting that working before dealing with the 3.2 api changes.

Most of the change in 3.2 is optional. That is, the new query API is something you don't need to change to right away. The changes in 3.1 around configuration and injection tend not to affect a lot of your code, but they are something you can't avoid dealing with.

Ari


-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: Upgrading from 3.0

Posted by Andrus Adamchik <an...@objectstyle.org>.
If you are generally ok with some APIs still evolving and changing between milestones, then go 3.2. You will have fewer generics warnings, etc. 3.1 is stable of course.

A.

On Sep 20, 2013, at 5:52 PM, Mike Kienenberger <mk...@gmail.com> wrote:

> Never mind.   After reading the news posting on the 3.2 release, I see
> that it builds on 3.1, so I'm better off upgrading to 3.1 first and
> getting that working before dealing with the 3.2 api changes.
> 
> On Fri, Sep 20, 2013 at 10:47 AM, Mike Kienenberger <mk...@gmail.com> wrote:
>> So I'm looking at upgrading from 3.0.2 to 3.1 or 3.2.
>> 
>> I can already see that there's a lot of Configuration-related changes
>> I am going to have to make.
>> 
>> Is it easier to upgrade to 3.1 then 3.2, or from 3.0.2 to 3.2 directly?
>> 
>> The 3.2M1 package does not contain upgrade notes for 3.2, but only up
>> through 3.1.
> 


Re: Upgrading from 3.0

Posted by Mike Kienenberger <mk...@gmail.com>.
Never mind.   After reading the news posting on the 3.2 release, I see
that it builds on 3.1, so I'm better off upgrading to 3.1 first and
getting that working before dealing with the 3.2 api changes.

On Fri, Sep 20, 2013 at 10:47 AM, Mike Kienenberger <mk...@gmail.com> wrote:
> So I'm looking at upgrading from 3.0.2 to 3.1 or 3.2.
>
> I can already see that there's a lot of Configuration-related changes
> I am going to have to make.
>
> Is it easier to upgrade to 3.1 then 3.2, or from 3.0.2 to 3.2 directly?
>
> The 3.2M1 package does not contain upgrade notes for 3.2, but only up
> through 3.1.