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
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
[
http://jira.codehaus.org/browse/MOJO-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MOJO-1022:
Component/s: Plugin Submission
> javahelp plugin...
> --
>
> Key:
I would like to deploy the following plugin to the sandbox snapshot
repository in order to try to gain support:
http://jira.codehaus.org/browse/MOJO-1022
Can someone please tell me how to go about doing this? If I am not
authorized to do it myself then the source is here:
http://maven-javahelp-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Hi
Hi there,
I was busy with other open-source activities the last time and time is little
anyways. As the original author of the plugin I want to put my two cents in
here:
I started a new MOJO that aims to bring all these deployment packaging stuf
