Hello Mojo Developers,
We're using cobertura at my job, and we'd really like aggregation to
work. So, I picked up MCOBERTURA-65 and added some testing to it in
the hopes of a commit.
I just got bad news from Robert Scholte. There is a longstanding
problem of license friction with this plugin where the cobertura
license and the codehaus license don't play well together. The
original MCOBERTURA-65 patch already trangressed a 'what can you call'
boundary here.
Hypothetically, the patch could be reworked to stay in bounds.
However, it seems to me to be wasteful to build and maintain a maven
plugin for a fundamentally GPL component (cobertura) in an environment
that puts barriers on writing code that makes subroutine calls to GPL
code. To me, this is what github was invented for.
It's hard for my to justify the effort of reworking this patch to get
what I want rather than making a fork. My question is this. How many
other people are reading this email who might, in any circumstance,
contribute to the ongoing maintenance of a cobertura maven plugin? How
many of you would cheerfully join me in maintaining a copy on github
published via ossrh? In other words, what's the advantage, to anyone,
of keeping this code at codehaus?
--benson margulies
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
