jslint4java mit Homebrew installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• jslint4java

Projektgeschichte

The Maven POM records an inception year of 2007, Dominic Mitchell as developer, Google Code issue management, and GitHub as the source-control location. The archived project description and GitHub README describe it as a simple interface for detecting potential problems in JavaScript code.

Adoptionsgeschichte

The package was useful in the period before JavaScript linting consolidated around Node.js-based tools. Java shops could run JSLint from Maven or Ant without introducing a separate JavaScript runtime into the build.

Wie es verwendet wird

Typical usage was running the jar from the command line against JavaScript files, wiring the Ant task into an Ant build, or using the Maven plugin during a build phase to fail on lint errors.

Warum Paket-Nerds sich dafür interessieren

jslint4java is a small fossil from the Google Code and Java build-tool era: a Java wrapper that made a JavaScript quality tool fit Maven Central, Ant, and distro packaging before npm-based linting became the common packaging path.

Zeitleiste

• 2007: The upstream Maven POM records the project inception year.
• 2011: Version 2.0.0 appears in the Git tag series.
• 2013: Version 2.0.5 appears as the later tagged release in the upstream repository.
• 2015: Google Code shuts down project hosting, leaving the Google Code Archive page as the historical homepage.

Related projects

• jslint4java wraps Douglas Crockford's JSLint and relates to Java build integrations such as Ant and Maven. It predates the broader shift toward Node.js linters such as JSHint, ESLint, and npm-distributed command-line tooling.

Quellen

• https://central.sonatype.com/artifact/com.googlecode.jslint4java/jslint4java-parent/2.0.2
• https://code.google.com/archive/p/jslint4java
• https://github.com/happygiraffe/jslint4java
• https://github.com/happygiraffe/jslint4java/blob/master/pom.xml