I was making incremental changes to the data model and moving forward nicely ... modify DDL, reverse engineer, test, ... wash, rinse, repeat. I the shut down the Roo shell and restated it and got "Cannot present nested annotations unless created by this class".
Note that everything had compiled and tested with zero errors previously. And it still compiles and tests without any errors. But I am now dead-in-the-water because Roo will ...
(a) not reverse engineer anything ... updates the dbre.xml file and then decides it will throw in the towel and unmanage it
(b) yet still makes changed to the some, but not all xxx_Roo_DbManaged.aj files.
Example would be to put the code that is in xxx_Roo_DbManaged.aj for an "ENABLED" column into xxx.java. Roo removes the code from xxx_Roo_DbManaged.aj. I then change the name of the column in xxx.java. Roo then regenerates the entry back in xxx_DbManaged.aj. So it only sort of gave up on managing the code. So it knows something about what WAS in the database but given that it unmanaged the dbre.xml file it can not get current, correct information.
I would gladly fix what ever it is in my code that causes the "Cannot present nested annotations unless created by this class" but have absolutely no clue what Roo is upset about and "this class" is not very specific.
And of course I could remove @RooDbManaged but that defeats one of the big reasons we are using Roo in the first place.