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
selecte
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 us
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 rest
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
I did 1.a ... after I got the preferences restored/working, I set up
everything the way I wanted and then did a backup in Time Machine so
I'd have a working version again if I had to restore.
For 3.1, we'll be switching over to the Java Preferences API instead
of XML files.
mrg
On Mon, Mar 29,
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
John,
I have been using Cayenne for a few years now, and have had to delete this
".cayenne" directory a few times. I guess I assumed that Cayenne 3.X addressed
this.
Thanks,
Joe
On Mar 29, 2010, at 12:44 PM, John Armstrong wrote:
> I see this as well.
>
> I also saw this behavior in some
Michael,
Thanks, I think I remember this being a previous problem. So I just deleted
the entire ".cayenne" directory, and now it saves the datasource configuration
correctly (well at least for this one project). Thanks.
So, my next question is:
1. Until 3.1 re-design, what steps should I no
I see this as well.
I also saw this behavior in some of the early M-series and think it had to
do with preference corruption or old vs new style prefs?
John-
On Mon, Mar 29, 2010 at 9:42 AM, Joe Baldwin wrote:
> More info:
>
> Cayenne Version: cayenne-3.0RC2
> OS: OSX
> CM: OSX
>
> I just did a
You are probably running into a known issue CM has with HypersonicSQL
(the embedded database Cayenne uses to save preferences -- an "eat
your own dogfood" kind of thing). Unfortunately, the simplest thing
to do is delete the preferences DB and start over. If you look in
your ~/.cayenne/prefs/1.2
More info:
Cayenne Version: cayenne-3.0RC2
OS: OSX
CM: OSX
I just did a test:
From Local Datasources pane,
1. select "New"
2. fill in the fields
3. select "Test" (it was successful),
4. select "Save".
5. Close CM
6. Re-open project using CM
7. view Local Datasources
- the new datasou
I am having a problem with Cayenne Modeler - Edit Preferences - Local
DataSources.
I am working with three projects right now and have created three separate
project directories. I am using Cayenne Modeler to manage the datasource
design. Unfortunately when I move from one project to another
12 matches
Mail list logo
