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

Integration tests in GsonIT suite fail on Windows #129

Closed
khitrenovich opened this issue Oct 21, 2013 · 2 comments
Closed

Integration tests in GsonIT suite fail on Windows #129

khitrenovich opened this issue Oct 21, 2013 · 2 comments
Milestone

Comments

@khitrenovich
Copy link
Contributor

Here are the error messages from the first run of the test:

  expectedFilesWereCreatedTest[0](org.jsonschema2pojo.integration.generation.GsonIT): Parent directory for the expected files did not exist: src\test\resources\integration\output\GsonIT\src\test\resources\integration\input\schema\person
  createdFilesWereExpectedTest[0](org.jsonschema2pojo.integration.generation.GsonIT): Some files were generated but not expected
        There were no files to check! This most likely means that code generation completely failed.
  roundTripJsonTest[0](org.jsonschema2pojo.integration.generation.GsonIT): Failed to get example class because output directory is missing. This most likely means that code generation failed.
@joelittlejohn
Copy link
Owner

Thanks for reporting this! I need to remove this test as it uses stale generated Java files. I'm not sure what the path problems are here on Windows but I'm going to replace the whole thing with a simple alternative that does a round trip of some JSON data through a generated type via Gson.

khitrenovich added a commit to khitrenovich/jsonschema2pojo that referenced this issue Oct 22, 2013
Name normalization should differentiate between class names and property
names to avoid name collisions and resulted compilation errors (issue
joelittlejohn#129)
khitrenovich added a commit to khitrenovich/jsonschema2pojo that referenced this issue Oct 22, 2013
Name normalization should differentiate between class names and property
names to avoid name collisions and resulted compilation errors
@khitrenovich
Copy link
Contributor Author

@joelittlejohn Please ignore the "referenced" comments above - accidentally submitted the changes to the wrong branch and with the wrong issue number. Definitely, it was not a good idea to play with the code while being sick at home...

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