- This topic has 9 replies, 3 voices, and was last updated 18 years, 4 months ago by
.
-
Posts
-
Hi guys!
As an addicted Eclipse/MyEclipse user I have immediately jumped to MyEclipse 5.0M1. One of the things I have noticed right away is the missing “Remove All Validation Markers” contextual action. I am wondering if it slept out or it is just me not seeing it.
The action was really usefull for me, and not having it makes me a little annoyed :-).Can you please help me out?
./alex
—
:Architect of InfoQ.com:
.w( the_mindstorm )p.Thanks. I knew that, but I am not sure Clean project can be considered a valid alternative of Remove All Validation Markers. So, I am asking: should I read it: “yes we removed that functionality and the closest you can get is Clean project”.
tia,
./alex
—
:Architect of InfoQ.com:
.w( the_mindstorm )p.“yes we removed that functionality and the closest you can get is Clean project”.
Alex, we explicitly removed the operation because it was originally put in place to work around a bug we had with the underlying validation framework that should now be corrected. However, if it is still useful to you, can you provide us with a specific use case that demonstates how / why you use it? With a good use case I can open a bug report and likely get it back if it’s still useful. Since validation markers are supposed to be persisted until they are fixed, the only workaround to remove and regenerate them is to clean the project in M1.
If you’re using the ‘Remove’ command to simply hide the markers for a time, then perhaps the Filters… in the Problems view will be helpful in that regard? Or, are you doing something different?
The usage scenarion you are describing is almost the one I am using. I was using that piece to solve problems with external XMLs that weren’t validated. I did it in 2 different ways:
1/ set the resource as derived (no validation at all), but in this case when done I was not able to commit anymore those resources
2/ remove the markers so that I am sure that my project is oke, disregarding the problems in the dependenciesThe 1st option is still valid, but it has the same drawback. The 2nd one is not anymore available and the replacement Clean Project doesn’t solve my scenario.
The idea of using filters is quite interesting. However I haven’t figured out how can I use the filters to hide the problems/warnings on special resources.
hth,
./alex
—
.w( the_mindstorm )p.I was using that piece to solve problems with external XMLs that weren’t validated.
Are they being validated correctly now with 5.0M1? If not, can you give us an example that shows where validation doesn’t work correctly?
1/ set the resource as derived (no validation at all), but in this case when done I was not able to commit anymore those resources
We’re working on a better way to say “don’t validate this” that doesn’t conflict with source control.
The idea of using filters is quite interesting. However I haven’t figured out how can I use the filters to hide the problems/warnings on special resources.
Do they share any phrases in the description of the error?
Are they being validated correctly now with 5.0M1? If not, can you give us an example that shows where validation doesn’t work correctly?
Nope… but definitely this is not MyEclipse fault. I can see by myself the errors. Unfortunately, as explained these files are 3rd party dependencies and I cannot completely correct them.
We’re working on a better way to say “don’t validate this” that doesn’t conflict with source control.
Yes, I remember discussing about it. It’s good to hear that your are working on it.
Do they share any phrases in the description of the error?
Hey, I am not so stupid :-). Unfortunately not, so nothing I can do about it.
Looks like I’ll be one of those eagerly waiting for the M2../alex
—
:Architect of InfoQ.com:
.w( the_mindstorm )p.Seems like the best way to get you what you really want is to get a “don’t validate these files” enhancement that is not dependent on the “derived” flag. I’ll add this URL to the PR to increase its priority with your usage scenario.
Hi!
I see that Remove all validation markers got back in the final 5.0. Congrats for the decission. At least I have a way to see my JSP-s clean even if this bug is still valid: https://www.genuitec.com/forums/topic/5-0m2-jsp-validator-complain-include-jspf/#post-254750.
./alex
—
:Architect of InfoQ.com:
.w( the_mindstorm )p.
