|
Sort Order:
Can we add a status action (Done, In progress, To do, ...)? In the initial cut, there is a status column. patch to xdoc plugin.jelly to include the report in the default reports, and exclude roadmap.xml from being transformed as a user doc look great! how about... sorry, I noticed in the issue you already have (b) - just didn't see it on the example page at openJMS > how about... I actually like the way jira does it tho - as an annotation on the type image. I also like jira's images too, although I suspect atlassian would object if I copied them > c) cvs tag and branch information (what it was tagged I view the roadmap plugin as being a record of future releases. Past releases would be the domain of the changes report. I guess my comments apply to the changes report more than this then. But I wonder whether it would be better to integrate the two? Otherwise you would probably find you'd just be cutting and pasting to changes through from roadmap once a release is made. Better just to have a flag and generate two different files isn't it? I think that is possible with the reports, but I'm not quite sure... Either that, or the two reports use the same source file, transforming different sections of it. Yes and no. Having both changes and roadmap in the one report means you lose the ability to add xdoc <section> elements which only apply to one. And some cutting and pasting would be required anyway, in order to convert a roadmap element to a change element. I'm not sure what you mean about the xdoc section - why does it apply to only one? Are you referring to having one source file and two outputs or one source and one output? As for the changing from roadmap to changes - I'm not sure why can't they be the same format? There is the same basic set of elements, a flag to say if it is future or past (or perhaps a different tag like your original schema), then other information that might be different, but just becomes an optional element in the XML (or in your original schema, can be a different sequence I guess). What do you think? Maybe we could list out all the appropriate information for both reports and put together one source file format. I like the idea of producing two documents though. Theoretically (meaning I haven't tried it <body> ...supporting the above means that the changes/roadmap can't be in the same document, unless new tags are introduced e.g: Doesn't seem to be a lot of point to me. I think it would be easier to have 2 source documents. I don't have any problem with the same plugin generating both reports - seems like a sensible approach. Rolls the roadmap plugin into the changes plugin. This replaces the previous patches. Does the patch apply? And has it been tested? Patch for project.xml to include xalan Details from Tim: The changes.xsl replaces changes.jsl. The only other change that needs to be made is to project.xml, The openjms website has both reports: http://openjms.sourceforge.net/changes-report.html The changes report was generated to not include the dev column:
Tim This issue can be closed. The patch is out of date with respect to the changes plugin in RC1. reporter asked for it to be closed. Sorry to comment in a very old thread, but i'm looking for a plugin to do exactly this. There is some one? I take a look to changes plugin but it doesn't have anymore the roadmap functionality in M2. Can somebody point me to the right place? |
|||||||||||||||||||||||||||||||||||||||||
New Feature
Closed
Trivial
Roadmap doc plugin
, you can mix any xdoc element in the changes/roadmap reports, e.g:
initial cut of the roadmap plugin.