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

Report source location in error messages #145

Open
martiell opened this issue Feb 28, 2012 · 1 comment
Open

Report source location in error messages #145

martiell opened this issue Feb 28, 2012 · 1 comment

Comments

@martiell
Copy link
Collaborator

Steps

  • Create invalid XSD file with, for example, broken references.
  • Run scalaxb

Problem

  • scalaxb does not report the location of errors.

Expectations

  • scalaxb should report the location of errors, including file and line number.

Notes

  • This would be useful for adding error markers in Eclipse.
  • Error location information could be included in an exception. But ideally, it should report many error locations rather than simply the first encountered.
  • An API would be better than logging output.
@eed3si9n
Copy link
Owner

eed3si9n commented Mar 1, 2012

This is something to consider for the next big version that I've been calling try/dogfood.

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

No branches or pull requests

2 participants