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
Hiya there. Here is another enhancement suggestion:
It would be nice to be able to specify rulesets per project instead of globally. I have some projects that has very rigorous rules, like Javadoc'ing everything, and some project that has more lenient rules (personal pet projects, for example), where more things are allowed. Having to go to the global EasyPmd options and change the active rulesets every time you switch projects is quite cumbersome.
The text was updated successfully, but these errors were encountered:
It would probably be a nice enhancement, but I'm afraid it might cause further issues:
What about project-related NetBeans APIs? Would one still be able to integrate EasyPmd in projects targeting different kinds of technologies and languages? I should investigate that.
What should be done when multiple projects are open at the same time, with dedicated EasyPmd settings? There should probably be multiple engine instances loaded at once.
Global settings and per-project settings, how should they be related?
Anyway, I'll certainly consider this suggestion when working on the next major architectural revision of the plugin! ^__^
Hiya there. Here is another enhancement suggestion:
It would be nice to be able to specify rulesets per project instead of globally. I have some projects that has very rigorous rules, like Javadoc'ing everything, and some project that has more lenient rules (personal pet projects, for example), where more things are allowed. Having to go to the global EasyPmd options and change the active rulesets every time you switch projects is quite cumbersome.
The text was updated successfully, but these errors were encountered: