[
https://issues.apache.org/jira/browse/CAY-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870617#action_12870617
]
Andrus Adamchik commented on CAY-1434:
--------------------------------------
> Yes, in Eclipse IDE source folder adding is as simple as one click to "Use as
> source folder" in context menu so I think it's minor problem.
and then later when you do "mvn clean" from command line, Eclipse will get
seriously upset.
> Storing superclasses in SCM seems to me inefficient because changes are
> allowed only to subclasses,
> and continuous touching of generated subclasses in main sources root lead to
> extra data on commits
> and serious merging problems after schema changing by other developers.
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.
> 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.
