Ok, let's stop voting. I confirm this problem and actually have fix
for it. Hope new release files will be soon.
On Sat, Sep 23, 2017 at 4:48 PM, Andrus Adamchik wrote:
> Just found a new bug introduced in B2:
> https://issues.apache.org/jira/browse/CAY-2366
>
> I guess it is related to the CAY-
sorry, a little offtopic,...
would it be possible to release the 3.1.2 ?
Thank you
Amedeo
> On 25 Sep 2017, at 12:49, Nikita Timofeev wrote:
>
> Ok, let's stop voting. I confirm this problem and actually have fix
> for it. Hope new release files will be soon.
>
> On Sat, Sep 23, 2017 at 4:48
Yes, let's stop voting. Fix for CAY-2366 is ready for 4.0 and should
be just ported to 4.1 branch,
fix for project version validation is on it's way.
ServerRuntime creation should fail with a meaningful message if
project file has incompatible version.
On Sun, Sep 24, 2017 at 6:16 PM, Michael Gen
> On Sep 25, 2017, at 1:51 PM, Amedeo Mantica wrote:
>
> sorry, a little offtopic,...
It is not off-topic in a wider Cayenne scope, but let's use a separate thread
subject at least. I renamed the thread.
> would it be possible to release the 3.1.2 ?
I think yes, though we'll need to catch a
there was a PR (merged) in order to fix Primary key generation
https://github.com/apache/cayenne/pull/173
I'm currently using 3.1.2 from my local repo
Thank tyou
Amedeo
> On 25 Sep 2017, at 13:04, Andrus Adamchik wrote:
>
>
>
>> On Sep 25, 2017, at 1:51 PM, Amedeo Mantica wrote:
>>
>> so
I have partially started using 4.1M1-snapshot in production now and I did
have one problem that you should be aware of.
There is a difference in the data inserted between the old
CayenneDataObject and the new BaseDataObject. Previously any attributes
modeled as primitive values (boolean, int) tha
Hi John,
Thanks for sharing. This is rather important. We'll need to think of a strategy
to handle NULLs for primitives (maybe as simple as a Modeler warning ... I.e.
if you expect nulls, map a column as an object, not a primitive).
Andrus
> On Sep 26, 2017, at 12:22 AM, John Huss wrote:
>
>
We've discussed the new website before, and Ari posted a prototype. Based on
that we did some work on a more detailed design, which I'd liek to present here:
1. Home page: https://invis.io/EQDMPF5YP
2. Internal page: https://invis.io/TSDMPF64F
It modernizes the logo. It attempts to balance Apa
