Add a configuration parameter to allow code generation for specific classes #517

Closed
manish-in-java opened this Issue Oct 9, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@manish-in-java

We are using Spring Data heavily and have a large number of entity classes. We have looked at QueryDSL and like the approach it takes very much. However, our need is to use QueryDSL with only a handful of entities right now.

It would be good if there was a configuration parameter which could be used to indicate which entity classes should be used for code generation. This would be the opposite of the current APT plugin configuration parameter that allows excluding specific classes. I would suppose that the flow would work as follows:

  1. If neither the include nor the exclude parameter is set, the plugin should generate code for all available entity classes.
  2. If the include parameter is set and the exclude parameter is not set, the plugin should generate code only for those classes specified in the include parameter.
  3. If the exclude parameter is set and the include parameter is not set, the plugin should generate code for all classes except for those specified in the exclude parameter.
  4. If both the parameters are set, the plugin should generate code for only those classes specified in the include parameter and not covered by the exclude parameter.
@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Oct 11, 2013

Member

I added now includedClasses and includedPackages

Member

timowest commented Oct 11, 2013

I added now includedClasses and includedPackages

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Oct 20, 2013

Member

Released in 3.2.4

Member

timowest commented Oct 20, 2013

Released in 3.2.4

@timowest timowest closed this Oct 20, 2013

@timowest timowest added this to the 3.2.4 milestone Apr 13, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment