[Resend]
No, I believe you're incorrect. What's important here is that there's
no clover license made available here, nor is clover itself made
available. The pom holds clover plugin configuration and nothing
more, and I seriously doubt there are any issues with your pom
defining configuration for publicly-available maven clover plugins.
Nobody can run it unless they're a committer and can obtain the
Apache license, or unless they happen to have their own license.
If you still disagree, please point specifically to chapter and verse
stating that adding such configuration to your pom is illegal. If I
have this wrong, I'll happily back it out.
--steve
On Dec 20, 2006, at 9:09 PM, Carl Trieloff wrote:
Steve,
We can't integrate Clover into the codebase / toolchain. I would
suggest that we back this out as it does not meet Apache license
guidelines. I think if someone has clover they can run it and fix
issues however the license does not allow those issues to be
reported on JIRA, or in any public way.
Reading the Clover license, integrating this into a public project
is clearly in violation of the posted license.
Carl.
Martin Ritchie wrote:
Hey,
I saw the reset additions to the POMs for clover. Have we applied for
a non-commercial license so we can all benefit from these changes? or
am I miss reading the licence info:
http://www.cenqua.com/clover/licensing.html
Cheers
