Closed cyraid closed 6 years ago
I think we probably want to revert the logging to print the stack trace. I don't remember why we moved to change it to just print the exception message, but this isn't the first time it hasn't been a helpful message.
Any idea why the get-openapi-doc isn't working by chance?
I'm not certain. Are you using Maven or Gradle? You could use a build plugin instead. It might help.
I'm using neither, just IntelliJ IDEA Ultimate. Would be nice to have it built into the editor. This is the reason I'm using the CLI (instead of maven/gradle).
It turns out --output was a pointing to a directory and not a filename. It's my bad, I suppose this could be left open for the better errors? Seeing as output is used as a directory as one option and a file as another, perhaps detecting if it's a directory, to add openapi.json? Or just output an error saying "path needs to be a filename" or something?
I added some more error checking as well as printing a full stack trace, rather than logging the exception message.
Hi there,
When I ran the tool with:
It responds with:
That's quite the error messages. :/ I've been struggling with this for awhile. It works when I generate with the "get-client-lib" though.. Here's what my SomeClass looks like:
Edit: Sorry I had a typo in the war directory in the get-discovery-doc, so I got that to work, but I double checked everything with the get-openapi-doc and it always responds with Error: null.