FLUP from #334

Currently, clicking edit on a configuration opens a dialog where you can change variables.
It'd be nice to be able to edit the name / file path too.

Currently we default to Checkstyle 7.1.2 and PMD 5.5.1, which are quite old (from September and July 2016, respectively). At the time of writing, Checkstyle is at version 8.8 and PMD at 6.0.1.

In Qulice 0.18.19, If I have this code:

    /**
     * constructor.
     * @param add {@link FieldAddition}
     * @param mul Field multiplication
     */
    public AbstractField(final FieldAddition<T> add,
        final FieldMultiplication<T> mul) {
        this.add = add;
        this.mult = mul;
    }

Qulice will complain with 2 violations:

• `First sentence in a comm

Some flag should be moved into the current statement context instead of being treated as a global value.

$this->_inFuncCall
$this->_inControlStatement
$this->_inFunctionStatement
$this->_inInterface
$this->_justAfterFuncStmt
....

We should know if we are inside a function statement with the context.

https://symfony.com/doc/3.4/templating/namespaced_paths.html

In the past, Symfony used to suggest using colons instead of @ namespaces. Adding a rule to check @ namespaces are being used instead of colons would be potentially useful

Prefer
@App/default/layout.html.twig
Over
AppBundle:default:layout.html.twig

Related: #180

This seems like a good pattern to follow for other embedded tools. Should we do it?

Proposed APIs:

gnag {
    // unchanged above here
    
    checkstyle {
        enabled true
        reporterConfig project.file('config/checkstyle.xml')
        toolVersion "X.X.X"
    }
    
    pmd {
        enabled true
        reporterConfig project.file('config/pmd.xml')

It would be cool to add a rule which detect operators like > or ++

// Valid  
if ((5 < x && x < 10)) { ... 
x = x + 1  
++x   
// Invalid  
if ((x > 5 && 10 > x)) { ...  
x++  

I have an eclipse installation with m2e but no eclipse-cs (I think).

We enabled checkstyle rules for our build and things seemed to work well.
Then I started seeing this weird error on my pom.xml:

It took me quite a while to realize that its saying there was a checkstyle violatio

when cs2pr completes and no errors/warnings have to be emitted, the screen stays empty.

as a user I dont know whether everything worked well and nothing had to be reported or there was a error and I dont see it.

at best we could emit a processed x errors and y warnings or similar status message at the very end into STDERR, so we dont destory possible consumers of our gihtub-api checks