This might take a while
I have been issueing quite a few commands in the roo shell from within STS, and like i said, they did not get appended to log.roo.
I also messed around with the project in other ways quite a bit (modified pom.xml, added webflow.version and spring security.version properties), so there can be many things causing this. I will try to get it replayable, but there's a few things i need to secure before that
Thanks a bunch for your help so far.
I completely deleted both the scaffolded controller, its views and the domain class, then regenerated both with roo.
STS 2.3.0 offers Roo command history recording. It is implemented by STS code as opposed to the normal Roo shell code. If it's not working with STS 2.3.0 would you please log a bug report and steps to reproduce at https://issuetracker.springsource.com/browse/STS. Thanks!
Is there a way to force Roo to regenerate my entity's aspects? In this case I just want to trigger the same generation that had occurred originally when I did "entity --class ...".
Though I have a Roo shell open while editing my entity's .java file, the generated code appears to be out of sync and this is why I am wondering if there is a "regenerate all decorations" trick.
Every time you start Roo it does an in-memory computation of what every ITD should have inside it, compares this with what is on disk, and if necessary updates the disk. You don't need to do anything special for this to happen. Just reload Roo and it will therefore do the equivalent of a "clean rebuild" for you.
OK, that's how I thought it should work. For some reason my Roo environment wasn't updating the ITDs, but I cannot reproduce it so for now I'll file this in the "probably will never know why" department. In the end I went with the nuclear option and restored from backup to a previous working state. The backup feature of Roo = win.
Thanks for the quick response,