cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Zeigler (JIRA)" <>
Subject [jira] Commented: (CAY-1181) Default class generation folder is wrong
Date Sat, 21 Feb 2009 11:11:46 GMT


Robert Zeigler commented on CAY-1181:

Now that CAY-1158 is fixed, it would be /really/ nice if the modeler would pick up the appropriate
java source directory automatically.  One way to do this would be to code logic directly into
the modeler that checks for a maven-like structure and "guesses" at src/main/java.  But I'm
not necessarily keen on this approach; true, src/main/java is /usually/ where the folder is,
but that's not written in stone.  In the context of CAY-1158, where the modeler is being loaded
directly by maven, it would be nice to have an external method of specifying the class generation
folder.  Perhaps an additional command line argument, or via a system property? Definitely
interested in getting a bit of discussion going on this b/c having to constantly change the
output folder is starting to get old; I have an itch to scratch on this one. 

> Default class generation folder is wrong
> ----------------------------------------
>                 Key: CAY-1181
>                 URL:
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: Cayenne Core Library
>    Affects Versions: 3.0M5
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
> Default class generation folder in the modeler (Tools > Generate Classes > Output
directory) is selected to be the folder where cayenne.xml is stored. If a user changes it,
it is not saved in user preferences, so on the next attempt to generate classes the old folder
is shown.
> Another related improvement: In a project that has Maven folder layout, cayenne.xml is
often is src/main/resources. In this case we must select a default folder ot be src/mainjava
(for "src/test/resources" it should be src/test/java). I.e. we should be smarter when we are
dealing with predictable maven structures.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message