Is this repository still actively maintained?

[ataraxie]

I just added it to my Maven project, but I discovered that the last supported JSHint Version is 2.5.6 and the last contribution was 2 years ago. Is this project still alive?

[friedbrice]

Evidently, we're using various version 0.0.x in production. I don't see where we're using 1.6.1, if at all. The original primary author has moved on to management, so I doubt anything new is on the horizon for this project. Sorry :-/

[bvarner]

I've had a Pull Request open for about a year and a half, with feedback from other devs that it was helpful. I'm guessing this is well and truly dust-binned.

Sadly.

It wouldn't take a lot of care and feeding to update, would it? @friedbrice Anyone have thoughts on a transition plan to get a new maintainer?

[friedbrice]

I'll ask around about finding a new maintainer, @bvarner

[spyhunter99]

@cjdev ping. i'll volunteer. Or fork it, merge the pr's and publish a release.

[paulrutter]

For future reference; i would opt to leave jshint and go for the leading eslint. Since there is no proper maven plugin, one can use the exec-maven-plugin to run it yourselves from maven.

            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>exec-maven-plugin</artifactId>
                <version>1.2.1</version>

                <configuration>
                <executable>node</executable>
                <workingDirectory>
                    target/${targetDir}
                </workingDirectory>
            <arguments>
                    <argument>./node_modules/eslint/bin/eslint</argument>
                    <argument>./**/*.js</argument>
                </arguments>
                </configuration>
                <executions>
                    <execution>
                        <id>eslint</id>
                        <phase>process-classes</phase>
                        <goals>
                            <goal>exec</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

In your project, make sure "eslint" and "eslint-cli" are installed in the directory you're trying to run it from. And, of course, nodejs needs to be installed. Although not a fix for this project, it provides your JS linting issues with an alternative that is being updated quite often.

[delanym]

https://github.com/eirslett/frontend-maven-plugin