Search:

Is there a way to support a flat multi module with roo.
By flat I mean that the root module is at the same level with the other modules and they are defined in this way:
<modules>
...

Thanks, I will try it, but anyway I don't think my use case fits into the multi-module schema. I want to use this library for different projects. I was planning to have it as a normal dependency.

Yes, that obviously works, but what is the reason? Are only the Roo annotated superclasses scanned?
This will explain it since the Roo annotations are with source retention.
I'm having something...

How is exactly the scanning for @Version and @Id done.
I have @MappedSuperclass that have @Version and @Id fields. This class is in separate module that is referenced as a dependency.

I inherit...

OK, I think I got the issue. The retention policy of the @RooJpaActiveRecord is source.

I have the following issue:
I have let's say module 1- it contains a MappedSuperclass. All roo entities that are defiled in module 1 work fine with the MappedSuperclass.
Now I have module 2 - I...

I have a MappedSuperclass that contains the id and version. I have no problem extending it within the same project, but if I want to reference it from external project, it does not work because roo...