> - in several plugins there are wrong <version> tags. Here's > what I typically find:
A bug in the changes plugin, already fixed. > - It's missing the download link for the new version in > navigation.xml. For example, for the 1.1 release of > aspectwerkz plugin: I propose we remove all of these. Users should use plugin:download. We have the changes document to say which releases are avilable and can do as you do on the cactus plugin, announcing the latest version on the front page. > - Sometimes, the new versions have not been created in the > JIRA project. Say I'm releasing version 1.1. We need to add a > new 1.2 version to that JIRA project. Yep, it'd be nice to use the SOAP interface to JIRA to do this, but currently half of them didn't even have the old version. This needs more attention from the plugin owners. > - Of course, I really don't like the modifications to > changes.xml where the lines are not wrapped and all <action> > are on one line. It makes it very difficult to read :-) It > has also wrecked all my careful indentations that I had set > over the past 2 years on all the plugins I was managing... :-( As I said last time, if you can figure out a way to get DOM4J to format it nicely, you can fix it. I was thinking I'd add a changes:add goal that interactively lets you add an element to changes.xml, and then you never need to edit it again. And in the future we will have GUIs for all this stuff and never need to edit XML again... - Brett
