[
http://jira.codehaus.org/browse/MRMIC-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211094#action_211094
]
Eric Haszlakiewicz commented on MRMIC-27:
-----------------------------------------
Every project I've worked with has considered "something that is wrong" to be a
bug (or "defect"), whether it's a code bug or a documentation bug, and
"improvement" (or "enhancement") to mean "it's working fine as it is, but this
change would be good to have".
IMO, documentation is a critical part of the plugin, as it is what specifies
how the code should work, so whether the eventual fix is code changes or
documentation changes it problem falls into the same category.
Of course, it only really matters if issues sit around open for a while and you
need to prioritize which ones to work one. When things get fixed this quickly
the terminology becomes irrelevant. :)
> The example for the package goal is broken
> ------------------------------------------
>
> Key: MRMIC-27
> URL: http://jira.codehaus.org/browse/MRMIC-27
> Project: Maven 2.x RMIC Plugin
> Issue Type: Improvement
> Reporter: Eric Haszlakiewicz
> Assignee: Paul Gier
> Priority: Minor
> Fix For: 1.1
>
>
> The example for the package goal described on
> http://mojo.codehaus.org/rmic-maven-plugin/usage.html is missing the
> "configuration" element around the excludes.
> It also needs a "<phase>package</phase>" element so it doesn't try to execute
> before the rmic compilation, and the id should be different from the compile
> example's id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
