IANAL,

If the GPL code has tainted the macker-maven-plugin, then we need to change
the license on macker-maven-plugin to GPL... a change that AFAIK is possible
(i.e. you can go ASL-2 -> GPL you just cannot go GPL -> ASL-2 )

I guess the question is has it been tainted?

When dealing with GPL libraries, if you want to keep yourself taint free the
best way is to interface via an API that has multiple implementations, that
way you can prove that the GPL code is only dynamically linked with your
code and as there are non-GPL implementations of the API, everything is
hunky-dorey

As java is all dynamic linking (except for uberjars) the question of taint
basically boils down to what API the library you are using is... for
example, if you write a JDBC client, IANAL but my understanding is that it
can safely be ASL-2 even if 99.99% of the time it is using a GPL JDBC
driver.

So for example with the vcc.dev.java.net project, I have designed a
virtualization api independently from any of the implementations... the api
is ASL-2... the fact that the xen implementation of the api will have to be
GPL is OK, because I have the ASL-2 licensed VMware implementation as the
reference implementation.

-Stephen

On 16 May 2010 11:58, Mark Struberg <[email protected]> wrote:

> Hi!
>
> I recently tried to help with the macker-maven-plugin [1] and figured that
> macker [2] itself (the underlying library being used) is GPL licensed.
>
> So, since the Mojos in macker-maven-plugin import files from the macker
> library, this imo conflicts with the ASL-2 license used in the
> macker-maven-plugin. Do be more specific, the macker-maven-plugin being
> ASL-2 licensed conflicts with the GPL license.
>
> So, what to do?
>
> LieGrue,
> strub
>
> PS: please note the distinction between GPL and LGPL and ClasspathGPL.
>
>
> [1] http://mojo.codehaus.org/macker-maven-plugin/
> [2] http://www.innig.net/macker/
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

Reply via email to