You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2010/05/24 15:54:23 UTC
[jira] Commented: (CAY-1434) Different destDir for generated
superclasses
[ https://issues.apache.org/jira/browse/CAY-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870610#action_12870610 ]
Andrus Adamchik commented on CAY-1434:
--------------------------------------
while I do not mind adding this for completeness, the specific example cited seems unusual... How do you prevent your IDE from complaining when subclasses have no superclass? Mapping target/generated-classes as a source folder?
> 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.