You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, whenever there is any error due to MANIFEST.MF, a long list of error stack in shown in Problems tab in alphabetical order according to the error message like here
Here the main issue exist in MANIFEST.MF(here incorrect bundle name in Require-Bundle and some extra lines)
Similar to this, there could be long error stack showing multiple java files in resource and MANIFEST.MF lost somewhere between them. Looking from a Java developer point of view, the error stack should directly take me to MANIFEST.MF. But as it is not on top of the error stack, the developer might get lost in other unnecessary places by following the order of the error stack.
To increase user experience, one solution could be:
To bring the error where resource is MANIFEST.MF to the top. As the current stack it alphabetically sorted, can we prioritise the ones where resource is MANIFEST.MF and take them to top? And in case there are multiple with MANIFEST.MF, it can be sorted according to the error message alphabetically.
Any suggestions if it can be taken up or if there is any other way to enhance this?
Also is it feasible from Platform side?
The text was updated successfully, but these errors were encountered:
Error markers are independent and as you can see one is from "Plugin Problem" (PDE) type and another from "Java Problem" Type (JDT). Also there is no way to tell that the manifest error is a causing the other problems.
So long story short, I don't think it is really possible with the current architecture. You can probably sort the list by type to see one category of problems first, but there is nothing one can do in general as one would then need some kind of "priority" to sort first (and a new column)
Right now the default sorting is done based on error message head in alphabetical order which doesn't have any such use. Should we change the default sorting based on 'Type' which will make it easier for user to point out where the error is coming from.
Right now, whenever there is any error due to MANIFEST.MF, a long list of error stack in shown in Problems tab in alphabetical order according to the error message like here
Here the main issue exist in MANIFEST.MF(here incorrect bundle name in Require-Bundle and some extra lines)
Similar to this, there could be long error stack showing multiple java files in resource and MANIFEST.MF lost somewhere between them. Looking from a Java developer point of view, the error stack should directly take me to MANIFEST.MF. But as it is not on top of the error stack, the developer might get lost in other unnecessary places by following the order of the error stack.
To increase user experience, one solution could be:
To bring the error where resource is MANIFEST.MF to the top. As the current stack it alphabetically sorted, can we prioritise the ones where resource is MANIFEST.MF and take them to top? And in case there are multiple with MANIFEST.MF, it can be sorted according to the error message alphabetically.
Any suggestions if it can be taken up or if there is any other way to enhance this?
Also is it feasible from Platform side?
The text was updated successfully, but these errors were encountered: