I do have a project which includes ZF library. In the problems tab I get all the warnings from the Zend library.
My problem is that I want to hide all that.
I've tried adding Exclude Group settings and rules for HTML for PHP validator and even I've suspended all validators for global settings and as a customized project settings and nothing works.
The strange thing is that most common type of problem is DLTK and I cannot find this particular validator.
Not all things in Eclipse that validate are validators. A lot of validation comes from builders. It is quite easy to disable a builder, but there could be unintended consequences if the builder is supposed to generate artifacts in addition to validation. To disable a builder, go to Project Properties -> Builders and uncheck it.
As an alternative, some tools that include builders allow you to specify that certain types of problems should not be reported. I am not familiar with PHP tools, but I would poke around under preferences.
Related
We recently decided that we want to share our Eclipse warnings settings so that all developers use the same ones (also save actions and formatter configuration). This of course means we want to remove all project specific settings. We created all the necessary plug-ins from scratch and are now able to display problems with quickfixes whenever project specific settings are still present.
So we now came to know that M2E selects the checkbox "Enable project specific settings" for the preference page "Java Compiler -> Errors / Warnings" on any Maven update (which usually happens quite often).
(Or adds the key value pair org.eclipse.jdt.core.compiler.problem.forbiddenReference=warning to .settings\org.eclipse.jdt.core.prefs.)
I think it's clear that it's absolutely unacceptable for a build tool to create project specific settings of any kind, much less to tinker with the forbidden references.
So how do I prevent M2E from doing just that?
Is there any built-in way (or plug-in) allowing for searching through the whole variable tree without manually expanding nodes?
I can't understand why isn't it done by default, just as I can't understand, why isn't search bar built into Variables view (browser style) and this unhandy, inconvenient dialog is opened instead. It makes my work, which is mainly debugging complex applications, a nightmare.
The Eclipse version is Luna, if it matters.
The watch expression feature is not what I want because it just doesn't work in this case, tried to fix it but none of the common ways to do that help me.
Such a feature has been requested earlier here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=170396
You may want to reopen this bug to state your interest in this enhancement. And if you have experience in developing Eclipse IDE plug-ins, I am sure the maintainers would be happy to review a patch.
I usually use Alt+Shift+Right/Alt+Shift+Left and Ctrl+Shift+I to select and inspect variables and expressions, but this certainly depends on personal preferences.
I want to write build.gradle in Eclipse and I need following support for that.
I need to write proper Groovy code to handle the complete build system and to deal with a certain file editing part. I want a support in eclipse which will show me all the methods available in dropdown for a particular class after typing classobject (methods dropdown). I want it to be the way it supports for Java programs.
I tried to add a couple of plugins in Eclipse, but they are not providing me this dropdown support. What plugin would work for this?
In order to speed up the eclipse, we can disable one or more validators in Eclipse IDE. It actually speeds up the loading of eclipse.
My question is not how to disable those validators. I know how to do that.
My question is What do those validators do? Why do we need them? What is the danger of disabling those validators? If we do not want them, why does eclipse comes with them?
If we use a build tool like ant to build our project, does disabling those validators still have any effect?
Quoting the offcial docs for juno
The validators used depend on the global and project validation settings. When you validate a project manually, the global settings are used unless both of the following are true:
The Allow projects to override these preference settings check box is selected on the global validation preferences page.
The Override validation preferences check box is selected on the project's validation preferences page.
What does that actually mean?
Validators are a feature of the Web Tools component of Eclipse. They provide a mechanism for checking the correctness of various file types (such as HTML, CSS, XML, JavaScript).
For file types such as Java the correctness of the file is determined when it is compiled, but there is no compiler for file types such as HTML so a different mechanism is need to check the files are correct. The validators provide this mechanism.
So if you turn of a validator you will longer get some messages about errors in files.
I would like to disable a read more plugin ( cutof content) in all pages except my main menu pages in joomla
How do I do this
Thanks in advance
I'm not aware of any method that allows for the actual disabling of a plugin for certain pages. Plugins are either on or off, site-wide. This can be seen from the Extensions | Plugin Manager, as well as the SQL database: jos_plugins. With that said, what would be the purpose in disabling a plugin for certain pages? Most plugins, especially those like a "readmore" are typically setup to be activated by a simple code sequence, such as {readmore}path/file.htm{/readmore} and consequently, you can turn the plugin "off" by simply choosing to not use it. Most plugins of that nature provide very little more than essentially "coded access to a CSS class". If you could be more specific on why you need to actually disable the plugin for certain pages, perhaps we'd be better equipped to answer properly.
Depending on the plugin, you could feasibly remove the event trigger that would set the plugin to run, thought it would not be advisable since it would stop that trigger for all plugins and could cause unintended effects.
I am not sure what you mean by "Read more" plugin. You can turn the read more text on and off as a setting in the menu item parameters or in the article itself. Have you tied that?