Roo stopped working - Undo managing

[vandegl]

When I start roo in the project structure I always get this:

    ____  ____  ____
   / __ \/ __ \/ __ \
  / /_/ / / / / / / /
 / _, _/ /_/ / /_/ /
/_/ |_|\____/\____/    1.1.2.RELEASE [rev fbc33bb]


Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
[FelixDispatchQueue] Undo manage SRC_MAIN_WEBAPP\WEB-INF\i18n\application.properties
[FelixDispatchQueue] Unable to obtain physical type metdata for type be.mydomain.project.web.File
roo>

Roo doesn't do anything anymore. Doesn't manage his files, doesn't create aj files,... It's impossible to continue with the project at this point.

I've tried:
- deleting the file "application.properties"
- emptying the file 'application.properties"
- a fresh checkout of the project and starting roo
- re-installing roo 1.1.2
- installing roo 1.1.3
- deleting the hidden file ".spring_roo_pgp.bpg" in my users folder

Nothing worked...
Does anyone know the problem, and how to fix it?

[vandegl]

Tried a fresh checkout on a new, clean pc and still nothing...

The project works fine with the previous aj files, so the code is valid. A checkout from a week ago works fine with Roo though.

Is it possible Roo "hangs" over some reserved words or something else while parsing my files?

[vandegl]

We isolated the problem to this:

imports from our own project should be fully named

This is what we had:

com.mydomain.model.*

When we declare seperate imports for each model entitiy the problem disappears.

Browsing through the Bug files one of the developers said this:

. It is essentially a usage requirement of Roo to not use wildcard imports in your source code.

Please insert this requirement into the coding conventions for Spring Roo, as working with a IDE grouping imports happens automatically. And we had no clue this could generate such major problems.

[boeckt]

Thank you very much! This totally solved the problem I was having!

Indeed this would be a nice addon to the coding conventions.

[levent.bayindir]

I agree. This should be documented clearly. Or a warning should be given at Roo shell when Roo detects this.

[vandegl]

Seriously, no response of any of the developers?
I really think this is a major issue, and it should be addressed asap. I strongly believe I am not the only one who had this problem, as the two responses above imply.

It is not that hard to just put it with the coding requirements...