[
https://issues.apache.org/jira/browse/CAY-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870640#action_12870640
]
Victor Antonovich commented on CAY-1434:
----------------------------------------
> and then later when you do "mvn clean" from command line, Eclipse will get
> seriously upset.
Yes, but next "mvn compile" will make Eclipse happy again. :)
> Wait a minute. Why would " continuous touching of generated subclasses"
> occur? It only happens when the model changes. Even if you run cgen multiple
> times over the same model, it would generate the same sources over and over,
> so no SCM commit will happend. From my long experience this is never a
> problem.
We had serious problems with working copies after removing generated classes
from Subversion repository. `svn update` checks timestamp of files in working
copy, so touched by cgen subclasses are treated by subversion as changed and
never removed from filesystem. Manually removing of stale generated classes was
really pain, especially on remote working copies in CI system.
> Different destDir for generated superclasses
> --------------------------------------------
>
> Key: CAY-1434
> URL: https://issues.apache.org/jira/browse/CAY-1434
> Project: Cayenne
> Issue Type: Improvement
> Components: Core Library
> Affects Versions: 3.1M1
> Reporter: Victor Antonovich
> Attachments: superclass_destdir.patch
>
>
> In some cases classes and superclasses should be generated to different
> directories. In example, superclasses should be generated to
> /target/generated-classes out of SCM scope, while subclasses are stored in
> main source tree (/src/main/java) under version control.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
