The first time I run the Roo 1.1.5 shell on your project, I get this output:
Code:
aswan: clientes > roo115
____ ____ ____
/ __ \/ __ \/ __ \
/ /_/ / / / / / / /
/ _, _/ /_/ / /_/ /
/_/ |_|\____/\____/ 1.1.5.RELEASE [rev d3a68c3]
[org.springframework.roo.classpath [50]] ServiceEvent REGISTERED
Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
Created SRC_MAIN_JAVA/com/clientes/XxxPK.java
Created SRC_MAIN_JAVA/com/clientes/Xxx.java
Updated SRC_MAIN_WEBAPP/WEB-INF/i18n/application.properties
Created SRC_MAIN_JAVA/com/clientes/XxxPK_Roo_Json.aj
Created SRC_MAIN_JAVA/com/clientes/XxxPK_Roo_Serializable.aj
Created SRC_MAIN_JAVA/com/clientes/XxxPK_Roo_Configurable.aj [org.springframework.roo.addon.solr [41]] ServiceEvent REGISTERED
Created SRC_MAIN_JAVA/com/clientes/XxxPK_Roo_Identifier.aj [org.apache.felix.framework [0]] FrameworkEvent STARTED
Updated SRC_MAIN_JAVA/com/clientes/ClientesPK_Roo_Identifier.aj Downloaded 100% of roobot.xml.zip
Created SRC_MAIN_JAVA/com/clientes/Xxx_Roo_Configurable.aj
Created SRC_MAIN_JAVA/com/clientes/Xxx_Roo_Entity.aj
Created SRC_MAIN_JAVA/com/clientes/Xxx_Roo_ToString.aj
Created SRC_MAIN_JAVA/com/clientes/Xxx_Roo_DbManaged.aj
Updated SRC_MAIN_JAVA/com/clientes/Clientes_Roo_Entity.aj
Deleted SRC_MAIN_JAVA/com/clientes/Clientes_Roo_DbManaged.aj
Updated SRC_MAIN_JAVA/com/clientes/Clientes_Roo_ToString.aj
Updated SRC_MAIN_JAVA/com/clientes/web/ApplicationConversionServiceFactoryBean_Roo_ConversionS
Updated SRC_MAIN_JAVA/com/clientes/web/ClientesController_Roo_Controller. [org.springframework.roo.process.manager [59]] ServiceEvent UNREGISTERING
Updated SRC_MAIN_WEBAPP/WEB-INF/views/clienteses/list.jspx
Updated SRC_MAIN_WEBAPP/WEB-INF/views/clienteses/show.jspx
Updated SRC_MAIN_WEBAPP/WEB-INF/views/clienteses/create.jspx [org.springframework.roo.classpath [50]] ServiceEvent REGISTERED
Updated SRC_MAIN_WEBAPP/WEB-INF/views/clienteses/update.jspx
roo> q
... and if I immediately re-run it, I get this error:
Code:
aswan: clientes > roo115
____ ____ ____
/ __ \/ __ \/ __ \
/ /_/ / / / / / / /
/ _, _/ /_/ / /_/ /
/_/ |_|\____/\____/ 1.1.5.RELEASE [rev d3a68c3] [org.springframework.roo.addon.web.mvc.controller [45]] ServiceEvent REGISTERED
Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
Deleted SRC_MAIN_JAVA/com/clientes/Clientes.java
Deleted SRC_MAIN_JAVA/com/clientes/ClientesPK.java
Deleted SRC_MAIN_JAVA/com/clientes/ClientesPK_Roo_Serializable.aj
Deleted SRC_MAIN_JAVA/com/clientes/ClientesPK_Roo_Json.aj
Deleted SRC_MAIN_JAVA/com/clientes/ClientesPK_Roo_Identifier.aj
Deleted SRC_MAIN_JAVA/com/clientes/ClientesPK_Roo_Configurable.aj
Undo delete SRC_MAIN_JAVA/com/clientes/ClientesPK_Roo_Configurable.aj
Undo delete SRC_MAIN_JAVA/com/clientes/ClientesPK_Roo_Identifier.aj
Undo delete SRC_MAIN_JAVA/com/clientes/ClientesPK_Roo_Json.aj
Undo delete SRC_MAIN_JAVA/com/clientes/ClientesPK_Roo_Serializable.aj
Undo delete SRC_MAIN_JAVA/com/clientes/ClientesPK.java
Undo delete SRC_MAIN_JAVA/com/clientes/Clientes.java
Unable to obtain physical type metadata for type com.clientes.Clientes
roo> q
Whereas if I run the latest build snapshot (in dev mode, so it's more verbose), I get no errors:
Code:
aswan: clientes > roo-clean
____ ____ ____
/ __ \/ __ \/ __ \
/ /_/ / / / / / / /
/ _, _/ /_/ / /_/ /
/_/ |_|\____/\____/ 1.2.0.BUILD-SNAPSHOT [rev 53eb1ad]
Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
Updated ROOT/pom.xml [updated property 'roo.version' to '1.2.0.BUILD-SNAPSHOT']
Created SRC_MAIN_JAVA/com/clientes/Clientes_Roo_Jpa_Entity.aj
Updated SRC_MAIN_JAVA/com/clientes/Clientes_Roo_Entity.aj
Created SRC_MAIN_JAVA/com/clientes/Xxx_Roo_Jpa_Entity.aj
Updated SRC_MAIN_JAVA/com/clientes/Xxx_Roo_ToString.aj
Updated SRC_MAIN_JAVA/com/clientes/XxxPK_Roo_Identifier.aj
Updated SRC_MAIN_JAVA/com/clientes/Xxx_Roo_Entity.aj
Updated SRC_MAIN_JAVA/com/clientes/web/ClientesController_Roo_Controller.aj
Updated SRC_MAIN_JAVA/com/clientes/web/ApplicationConversionServiceFactoryBean_Roo_ConversionService.aj
roo> q
Total execution time 14.656 seconds
Roo exited with code 0
So my suggestion is to try the latest snapshot, and if it works for you, consider using that or the imminent 1.2.0.M1 release.