grails-maven-plugin issues

gistfile1.txt

http://jira.grails.org/browse/MAVEN-86
 - Fixed with commit 6e4e2ad, pull request 15

http://jira.grails.org/browse/MAVEN-118
 - Can be closed? grails-webflow no longer exists as a dependency

http://jira.grails.org/browse/MAVEN-84
 - Not an issue anymore? java.home is an exposed property from maven, and there are no more references to java.version

http://jira.grails.org/browse/MAVEN-68
 - Seems to be a non-issue.
 - I'm not sure this would want to be fixed.

http://jira.grails.org/browse/MAVEN-67
 - Old issue and the supplied patch doesn't seem to reference still-existing code
 - The paradigm of the hyphenated-to-camel-case from the command line still might warrant re-addressing in a case where you would want a plugin project with hyphenated names

http://jira.grails.org/browse/MAVEN-37
 - Bleh, easy fix. Pull requests to follow

http://jira.grails.org/browse/MAVEN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=71046#comment-71046
 - Appears to be unrelated to the issue & should be opened under another issue that reproduces the problem (and for the correct version 2.1.0.RC1)

http://jira.grails.org/browse/MAVEN-96
 - xml-apis contention, but should have a test app provided by Aaron Digulla to fully verify the issue

http://jira.grails.org/browse/MAVEN-113
 - reporter says the issue is resolved in 1.3.x and can be closed.

http://jira.grails.org/browse/MAVEN-144
 - I commented. This is a non-issue.

http://jira.grails.org/browse/MAVEN-18
 - This is almost certainly not a grails-maven-plugin issue and should be addressed as part of the ivy resolver.

http://jira.grails.org/browse/MAVEN-66
 - latest documentation included the list of excluded arte(i)facts

http://jira.grails.org/browse/MAVEN-6
 - old issue from grails 1.3.5

http://jira.grails.org/browse/MAVEN-1
 - there appears to be the appropriate way to manage this issue in the comments

http://jira.grails.org/browse/MAVEN-32
 - this doesn't happen in 2.0.3 version, so presumably it was fixed at some point and the issue not updated.