[
https://issues.apache.org/jira/browse/CAY-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870615#action_12870615
]
Victor Antonovich edited comment on CAY-1434 at 5/24/10 10:26 AM:
------------------------------------------------------------------
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. 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.
was (Author: kapyar):
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. 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 developer.
> 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.
