Hi Anders/Robert, I've updated the plugin to reflect the new name and updated the Mojo Site project to reflect its new link. I've also updated the Mojo site doco to reflect the artifactId and project naming guidelines discussed below.
However I'm unable to commit any of this because The Codehaus SVN is rejecting me (there's another email on that). As soon as it is back up I shall check in my changes to the two projects. Kind regards, Christopher On 19/08/2011, at 8:37 AM, Robert Scholte wrote: > Hi, > > > ArtifactIds at Codehaus should match the following pattern: > [project]-maven-plugin > The name is a bit trickier: > If the name of the project is copyright/trademark safe, you can use [Project] > Maven Plugin > Otherwise you should use: Mojo's Maven Plugin for [Project] or Mojo's > [Project] Maven Plugin > > -Robert > > Date: Thu, 18 Aug 2011 20:22:24 +0200 > > From: [email protected] > > To: [email protected] > > Subject: Re: [mojo-dev] [vote] Graduate the Maven JSLint Plugin version > > 1.0.0-SNAPSHOT > > > > 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 > > > >
