>> 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
I read it as the jira project should be created first and info included in the pom. That will make the info on the site correct. >> 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? Maybe change to "This plugin brings the JSLint JavaScript code quality control tool capabilities..."? >> * 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? No. It stays on the last released version. So 1.0.0 is what people will see and therefore it's important to get things right before releasing. >> * 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. If you just want to add a config (or dependency), you don't have to override the version. But possibly your config requires an older version of the plugin? In my opinion, the more standard mojo config we have the better. Solve it once, use everywhere kind of. But there might be places where this simply doesn't work. /Anders > > Kind regards, > Christopher > --------------------------------------------------------------------- > 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
