Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Upgrading from 3.0
From: Andrus Adamchik <andrus@objectstyle.org>
In-Reply-To: 
 <CAM1yOjZ0p435OHF=AdPrH4Tg2ZicNnkDX1brhq7Wmi-kHqf1uw@mail.gmail.com>
Date: Fri, 20 Sep 2013 20:38:08 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B66AB7A3-7EA7-4D69-9679-FF801B61FA38@objectstyle.org>
References: 
 <CAM1yOjbGWHHoNawq_WQYRx_Ybn3ZgnV4t9gjO_H90KBFKXSpmw@mail.gmail.com>
 <CAM1yOjZ0p435OHF=AdPrH4Tg2ZicNnkDX1brhq7Wmi-kHqf1uw@mail.gmail.com>
To: user@cayenne.apache.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 <mkienenb@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.
>=20
> On Fri, Sep 20, 2013 at 10:47 AM, Mike Kienenberger =
<mkienenb@gmail.com> wrote:
>> So I'm looking at upgrading from 3.0.2 to 3.1 or 3.2.
>>=20
>> I can already see that there's a lot of Configuration-related changes
>> I am going to have to make.
>>=20
>> Is it easier to upgrade to 3.1 then 3.2, or from 3.0.2 to 3.2 =
directly?
>>=20
>> The 3.2M1 package does not contain upgrade notes for 3.2, but only up
>> through 3.1.
>=20