[
https://issues.apache.org/jira/browse/CAY-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrus Adamchik updated CAY-2986:
---------------------------------
Description:
Currently, cgen checks for DataMap age vs. generated classes age and only runs
conditionally when the former is newer than the latter. Had a lot of issues
with this lately when doing map upgrades, and switching between Claude and IDE
(timestamps would get mixed up and cgen won't rerun when I need it).
So, let it run unconditionally. The whole lazy run optimization is useless
anyways. Cgen is idempotent and very fast.
This also means getting rid of "force" option (now it will always behave as
"force")
was:
Currently, cgen checks for DataMap age vs. generated classes age and only runs
conditionally when the former is newer than the latter. Had a lot of issues
with this lately when doing map upgrades, and switching between Claude and IDE
(timestamps would get mixed up and cgen won't rerun when I need it).
So, let it run unconditionally. The whole lazy run optimization is useless
anyways. Cgen is idempotent and very fast
> Cgen to run unconditionally
> ---------------------------
>
> Key: CAY-2986
> URL: https://issues.apache.org/jira/browse/CAY-2986
> Project: Cayenne
> Issue Type: Task
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Priority: Minor
> Fix For: 5.0-M3
>
>
> Currently, cgen checks for DataMap age vs. generated classes age and only
> runs conditionally when the former is newer than the latter. Had a lot of
> issues with this lately when doing map upgrades, and switching between Claude
> and IDE (timestamps would get mixed up and cgen won't rerun when I need it).
> So, let it run unconditionally. The whole lazy run optimization is useless
> anyways. Cgen is idempotent and very fast.
> This also means getting rid of "force" option (now it will always behave as
> "force")
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
