+1 for 1 :)
Summers Pittman wrote:
Do we want to
1) Put the workaround in the project's README until it isn't necessary
2) Host a patched version of the plugin on jboss nexus and configure the
pom to run against it
3) Post instructions for how developers can patch/update their local
install of the plug-in
4) Wait patiently until the fix makes it into central
5) Something else I overlooked.