False positive by lines-around-comment for JSDoc

Tell us about your environment

• ESLint Version: 5.2.0
• Node Version: v8.9.4
• npm Version: 5.6.0

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration:

Configuration

{
    "env": {
        "browser": true,
        "es6": true,
        "greasemonkey": true
    },
    "extends": "eslint:recommended",
    "globals": {
        "min": false
    },
    "rules": {
        "lines-around-comment": [
            "error", {
                "afterBlockComment": true
            }
        ]
    }
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

/**
 * Converts an array-like object to an Array.
 * @param {Object} collection - The collection to be converted.
 * @returns {Object[]} The resulting array.
 */
function toArray(collection) {
    return Array.prototype.slice.call(collection);
}

toArray([]);

eslint scripts/**/*

What did you expect to happen?

Not throw an error.

What actually happened? Please include the actual, raw output from ESLint.

...scripts/Main/main.js
  1:1  error  Expected line after comment  lines-around-comment

✖ 1 problem (1 error, 0 warnings)
  1 error and 0 warnings potentially fixable with the `--fix` option.

I think that it should make an exception for JSDoc. Meaning that /** */ is not actually a block comment, /* * */ is a block comment.

The current workaround is to use "ignorePattern": "\\*".

[revolter]

This is still an issue.

[kaicataldo]

Given that JSDoc support has been deprecated, JSDoc comments won’t have any special meaning to ESLint core rules going forward. If ignorePattern doesn’t solve the issue reported here, do you mind making a new issue proposing an enhancement that might?