Results 1 to 5 of 5

Thread: Roo 1.0.1 generating fully-qualified names

  1. #1
    Join Date
    Feb 2010
    Posts
    3

    Default Roo 1.0.1 generating fully-qualified names

    I've just switched to doing some prototyping in 1.0.1, and have noticed that rather than using imports to qualify the names of field types and annotation types, it has started to fully-qualify them all.

    Given that this is not typically how java looks, particularly entities, is there any way to go back to imports? I'd rather have neat, clean-looking entities.

  2. #2
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    667

    Lightbulb Known issue in 1.0.1?

    I think this is already logged as http://jira.springframework.org/browse/ROO-576?
    Andrew Swan
    "Now is the EJB of our discontent made glorious Spring"

  3. #3
    Join Date
    Mar 2008
    Location
    Sydney, AU
    Posts
    974

    Default

    Yes this was a regression introduced by one of Ben's changes. It should be fixed with the next release.
    Stefan Schmidt
    Software Engineer, Spring Roo
    SpringSource - a division of VMware
    twitter @schmidtstefan

  4. #4
    Join Date
    Feb 2010
    Posts
    3

    Default

    Ah, perfect. Didn't spot that. Thanks.

  5. #5
    Join Date
    Aug 2004
    Location
    Sydney, Australia
    Posts
    2,768

    Default

    Yeah, missed that one. But imports in the ITDs still work nicely. :-)

    We'll get a 1.0.2 out mid-February that will resolve it. In the meantime you can freely edit the .java files to make the imports as you like them. Roo never changes your .java files unless you ask it to via a shell command, and it will understand and retain any imports you have used.

    Sorry for the inconvenience in the meantime.
    Ben Alex
    Project Founder, Spring UAA, Spring Roo and Spring Security

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •