cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <and...@objectstyle.org>
Subject Re: Cayenne Modeler - Local DataSources
Date Tue, 30 Mar 2010 07:21:18 GMT
No I am talking about the "output directory" preference only.

Entity selections within a DataMap should work as before and are not  
preferences driven.

Andrus

On Mar 29, 2010, at 10:09 PM, Joe Baldwin wrote:

> Andrus,
>
> I seem to recall that CM used to generate code based on what was  
> selected (I may be wrong, but that is what I remember).  So that if  
> you had just one entity selected in a datamap, that was all that was  
> getting updated.
>
> But then I think that behavior might have changed.   Either way I  
> usually select the intended datamap with the intention that *all* of  
> that map's entities will be generated and the database tables will  
> be generated.
>
> Is this what you are referring to?
>
> Joe
>
>
>
>
> On Mar 29, 2010, at 2:59 PM, Andrus Adamchik wrote:
>
>> I just tried, starting with blank preferences and RC3 modeler.  
>> Initial (default) class generation output directories were  
>> different for different projects (guessed correctly based on the  
>> Maven project structure). Custom changes to those were stored and  
>> reloaded from preferences after a restart.
>>
>> I should mention though that these are stored not only per project,  
>> but also per DataMap within a project, so if you have more than one  
>> DataMap, customizations have to be applied to each one of the maps,  
>> otherwise Cayenne would suggest a default location.
>>
>> Also don't remember the default behavior for non-maven project  
>> structures, but that should not affect preferences behavior.
>>
>> Andrus
>>
>> On Mar 29, 2010, at 9:08 PM, Michael Gentry wrote:
>>
>>> Hmm, I just tried this with RC3 and it definitely changed my default
>>> output folder.  I had project A open with project A's output folder
>>> selected.  Then I switched to project B and it selected project A's
>>> output folder.  I'm not sure if this behavior has always existed  
>>> or if
>>> it is a new bug.
>>>
>>> mrg
>>>
>>>
>>> On Mon, Mar 29, 2010 at 1:20 PM, Joe Baldwin <jfbaldwin@earthlink.net 
>>> > wrote:
>>>> Michael,
>>>>
>>>> It appears that the "Code Generation - Output Directory" is  
>>>> having the same problem (i.e. it would revert to a previous  
>>>> directory after I changed it).
>>>>
>>>> Is this another issue having to do with the ".cayenne" directory?
>>>>
>>>> thanks,
>>>> Joe
>>>>
>>>>
>>>
>>
>
>


Mime
View raw message