Enforce right method parameters order in Javadoc

[HDouss]

For now, qulice accepts such javadoc -notice arg related javadoc precedes param related javadoc, although param parameter is declared before arg parameter in the signature-:

    /**
     * Constructor.
     * @param arg Arg
     * @param param Param
     */
    public MyClass(final String param, final String arg) {
        this.param = param;
        this.arg = arg;
    }

It would be better to enforce developers to write method (or constructors) parameterss javadoc in the order they appear in the signature.
Many times, the javadoc misleads about the order for which to call the method, especially when the parameters are in the same type.

[0crat]

@krzyk please, pay attention to this issue

[HDouss]

@krzyk Any news here ?

[krzyk]

@HDouss currently project is not founded, so no news

[krzyk]

@0crat in

[0crat]

@0crat in (here)

@krzyk Job #847 is now in scope, role is DEV

[0crat]

Bug was reported, see §29: +15 point(s) just awarded to @HDouss/z

[0crat]

@krzyk/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV are banned at #847; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV are banned at #847; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV is banned at #847; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV is banned at #847; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV is banned at #847; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV is banned at #847; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0pdd]

@HDouss the puzzle #1001 is still not solved.

[paulodamaso]

@HDouss Merged in #986, please close.

[HDouss]

@paulodamaso Thanks.

[0crat]

@ypshenychka/z please review this job completed by @paulodamaso/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

[0crat]

The job #847 is now out of scope

[ypshenychka]

@0crat quality good

[0crat]

@0crat quality good (here)

@ypshenychka The project doesn't have enough funds, can't make a payment

[0crat]

Order was finished, quality is "good": +35 point(s) just awarded to @paulodamaso/z

[0crat]

Quality review completed: +8 point(s) just awarded to @ypshenychka/z

[0pdd]

@HDouss the only puzzle #1001 is solved here.