Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Referenced nested classes not always in correct package #683

Open
sazzer opened this issue Jan 27, 2017 · 1 comment
Open

Referenced nested classes not always in correct package #683

sazzer opened this issue Jan 27, 2017 · 1 comment

Comments

@sazzer
Copy link

sazzer commented Jan 27, 2017

I'm trying to generate classes from JSON Schemas that are stored in a directory tree. Mostly this works great, but in some situations it seems that the classes aren't generated in the correct place.

I've narrowed this down to alphabetically the order that the schemas are found, rather than the directory they are found in. For example:

This works

  • src/main/schemas/common/identity.json
  • src/main/schemas/users/user.json --> References "../common/identity.json"

This doesn't work

  • src/main/schemas/common/identity.json
  • src/main/schemas/attributes/attribute.json --> References "../common/identity.json"
    • In this case, the "IdentityModel.class" file is placed into "/model/attributes/IdentityModel.class" instead of "/model/common/IdentityModel.class"
@sjohnr
Copy link

sjohnr commented Feb 8, 2017

+1. Working around this problem right now via javaType to specify the package that the class gets generated in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants