I'm inclined to vote -1 in the current state: * I think that the artifactId should be jslint-maven-plugin * I think that the name should be changed to "JSLint Maven Plugin"
This is based on a quick look, there could be other similar things. /Anders PS. I checked our dev guide lines and there's no guide about these things (but package name is mentioned). Should it be added? On Thu, Aug 18, 2011 at 13:11, Christopher Hunt <[email protected]> wrote: > Hi there, > > I'd like to graduate version 1.0.0-SNAPSHOT of the Maven JSLint Plugin (1) > from the sandbox. The plugin has been developed in the sandbox since > 27/Oct/10, now has an additional committer and is being used heavily within > at least one corporate environment. > > PROJECT_DESCRIPTION > This plugin brings JSLint capabilities to the Maven project lifecycle with > the goal of assuring JavaScript code quality. > > The Maven JSLint Plugin operates quickly and efficiently on modified > JavaScript source code. When used with IDE's such as Eclipse and its Maven > integration, developers can rapidly see JSLint problems reported in the IDE's > console as a JavaScript source file is saved. > > SCM Tag: > http://svn.codehaus.org/mojo/trunk/sandbox/jslint-plugin > > [ ] +1 > [ ] +0 > [ ] -1 > > The vote is open for 72 hours and will succeed by lazy consensus. > > Kind regards, > Christopher Hunt > > (1) http://mojo.codehaus.org/jslint-plugin/ > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
