Re: [mojo-dev] Plugin Change Log

2008-02-17 Thread Dennis Lundberg
Benjamin Bentmann wrote: The only time I think it is ok to *not* specify a version, is for issues that are not tied directly to a release. OK, in this case, one wouldn't want to show such issues in a release history. Does the maven-changes-plugin already provide a way to exclude such issues fr

Re: [mojo-dev] Plugin Change Log

2008-02-16 Thread Benjamin Bentmann
The only time I think it is ok to *not* specify a version, is for issues that are not tied directly to a release. OK, in this case, one wouldn't want to show such issues in a release history. Does the maven-changes-plugin already provide a way to exclude such issues from download/display? Be

Re: [mojo-dev] Plugin Change Log

2008-02-16 Thread Dennis Lundberg
Benjamin Bentmann wrote: I'm putting the final touches on the next version of maven-changes-plugin. Several enhancements have been made to the JIRA Report. It is now almost as configurable as a live JIRA "Change Log" view. Finally I got some time to play around with this. I used something like

Re: [mojo-dev] Plugin Change Log

2008-02-15 Thread Benjamin Bentmann
I'm putting the final touches on the next version of maven-changes-plugin. Several enhancements have been made to the JIRA Report. It is now almost as configurable as a live JIRA "Change Log" view. Finally I got some time to play around with this. I used something like Fix Version DESC, Type AS

Re: [mojo-dev] Plugin Change Log

2008-02-10 Thread Trygve Laugstøl
Benjamin Bentmann wrote: The changelog plugin would probably cover what you're after pretty good. Thanks for the pointer but my intent was not to show the SVN commits. I would like to show a user-friendly release history and at least I would not call something like [0] "user-friendly", it's jus

Re: [mojo-dev] Plugin Change Log

2008-02-10 Thread Dennis Lundberg
Benjamin Bentmann wrote: Hi, I would like to see some kind of change log in the plugin site (e.g. reachable via the "Overview" menu) such that users can easily figure out if they would benefit from a plugin update or if they need to watch out for modified behavior. So far, it seems quite no

Re: [mojo-dev] Plugin Change Log

2008-02-10 Thread Benjamin Bentmann
The changelog plugin would probably cover what you're after pretty good. Thanks for the pointer but my intent was not to show the SVN commits. I would like to show a user-friendly release history and at least I would not call something like [0] "user-friendly", it's just to technical for the use

Re: [mojo-dev] Plugin Change Log

2008-02-10 Thread Trygve Laugstøl
Benjamin Bentmann wrote: Hi, I would like to see some kind of change log in the plugin site (e.g. reachable via the "Overview" menu) such that users can easily figure out if they would benefit from a plugin update or if they need to watch out for modified behavior. So far, it seems quite no

[mojo-dev] Plugin Change Log

2008-02-09 Thread Benjamin Bentmann
Hi, I would like to see some kind of change log in the plugin site (e.g. reachable via the "Overview" menu) such that users can easily figure out if they would benefit from a plugin update or if they need to watch out for modified behavior. So far, it seems quite no plugin (Apache as well as