Lukas, thanks for the detailed response.
 
>
> In the past, Apache projects or Red Hat products concluded with not 
> proceeding with a jOOQ integration, because dual licensing was against 
> their general strategy / philosophy. This doesn't have to be the case for 
> you, though.
>
Dual licensing would not be an option for us either.

 
>
> Regarding your specific questions:
>
>  
>
> -          *Compile time requirements: Can oracle specific JOOQ features 
> be compiled with the open source version or does this require a commercial 
> JOOQ license?*
>
>  
>
> This will require a commercial jOOQ license, as most Oracle specific jOOQ 
> features are not available from the Open Source edition.
>
 
>
> -          *Runtime requirements: I guess at least here any contributor 
> who would want to run tests with Oracle would require a commercial JOOQ 
> license?*
>
>  
>
> Yes - although, do note that the commercial license is a floating license, 
> not a named user license. I.e. only as many licenses are needed as there 
> are contributors developing with *jOOQ at the same time*.
>

I am not sure how a floating license would be practical in a decentralized 
community based development model. The only option I can see here would be 
to use it on a CI server to make sure that the oracle integration tests 
still work. The killer however is the compile time dependency. I wasn't 
fully sure how the oracle features were implemented at the moment and I was 
hoping that its API would be exposed in the free version and it would 
simply fail to load implementations at runtime. This means that any oracle 
specific code would need to be completely separated into its own module 
that would be separately developed by JOOQ license holders.
 
Did you ever think of making JOOQ freely available for Oracle XE? To me 
this sounds like a win win, the open source community could use the 
goodness of JOOQ in the development of oracle targeted projects while JOOQ 
would sell licenses once people have to deploy them to an oracle production 
instance. In other words this would be 1 license per deployer, rather than 
1 license per developer.

Timm


-- 
You received this message because you are subscribed to the Google Groups "jOOQ 
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to