-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Show line number #45
Comments
I use a library called Jdom to parse the XML, and I think that this library doesn't support the concept of line numbers. I look into this further, but the chances are slim. |
The plugin works like this for verification:
The problem is that the element structure does not have access to the line number. I could try to locate the elements in the original file by using a line by line string comparison, but I cannot be certain that I get a unique match or even that I get a match at all (if element start or end is on separate lines). Sometimes the line number indication would point to the wrong line and sometimes it would be missing. |
I'm surprised that library didn't have information about line numbers. Is it something JDOM-specific or all the libraries have the same behavior? |
It is JDOM specific. It is an old library (think Java 1.4) and I don't have the time to change xml parsing library. Some of the plugin functionality is now directly dependent on that version of that library. |
Why not keep this issue open to be able to fix it someday in the next major release? |
Sorry mate, it won't happen. I don't have time to rewrite the plugin from scratch. It is no idea to keep issues open if I can't fix them within reasonable time. |
But others could see what can be done and might offer a pull request... |
To rewrite the plugin from scratch :-D How about if I create a wiki page that collects issues (epics) that can only be done sometime in the future? |
Sorry to say, but if you don't like it than do not make it open source ;-( But of course a wiki pages which collects issues like this would be another good idea...Or just assign the issues to an appropriate milestone like 3.0 ? |
@Ekryd did a good job by creating this plugin and it's ok that he doesn't want to accept some PRs because of some reason. Actually it's good that he said it as-is right now. It just means that if someone wants to implement it, he/she should fork this project instead of creating a PR here. |
Of course a fork is also a reasonable solution. |
I'd like to see on which line I have an error. At present, plugin shows only a message:
The text was updated successfully, but these errors were encountered: