Hi Anders, On 12/09/2011, at 4:12 PM, Anders Hammar wrote:
> A see that there is already a 1.0.0 tagged for this plugin. Is your > plan to release from that tag after this vote? Yep. > > The reason for asking is that I can't find the jira project for this > project, which a graduated project should have, and that info should > be added to the pom. So, unless I'm missing something I'd say -1 > releasing until things like this is fixed. I was told by Robert Scholte that it doesn't get a JIRA project until a first release is cut, and also: http://mojo.codehaus.org/development/performing-a-release.html#Preparing_for_the_First_Production_Release > > Some other things that need to be fixed: > * In the bread crumbs of the site it says "JavaScript Lint Maven > Plugin". The name should be concistent, so change this to "JSLint > Maven Plugin". Possibly you somewhere want to explain what JSLint > stands for. Hmmm. OK re bread crumb. On the JSLint subject, I really hoped that the first paragraph did just that; there is a hyper link there under "JavaScript code quality control". Is this not enough? > * The index pages says the plugin is still in sandbox. It's not. Fair enough - but won't the page get updated with 1.0.1-SNAPSHOT as soon as I release a snapshot again i.e. should it hold up the release of the plugin? > * The pom overrides the site plugin version declared by mojo-parent. Why? From memory I believe that this was because I wanted to use doxia-module-confluence (my site documentation is in Confluence). When declaring plugins I understand that best practice is to specify a plugin's version. Kind regards, Christopher --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
