Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Objenesis license incompatible with EPL #40

Closed
sophokles73 opened this issue May 18, 2016 · 4 comments
Closed

Objenesis license incompatible with EPL #40

sophokles73 opened this issue May 18, 2016 · 4 comments
Assignees
Milestone

Comments

@sophokles73
Copy link

Hi,

I am working on several Eclipse projects where we would like to use Mockito 1.9 which depends on Objenesis 1.0. The Eclipse Foundation has very strict rules regarding IP and license validation. In particular, a scan of the source code of third party dependencies is conducted before an Eclipse project can use it. In case of Objenesis 1.0 this has brought up a problem with the JRockit support classes which are licensed for use only under a license approved by the FSF (which the Eclipse Public License unfortunately is not). This makes it very hard for Eclipse Projects to even use Mockito and Objenesis for testing (not to mention re-distribute it). Some people have started to strip out the offending classes and keep a copy of the modified source code in their projects.

Is there a way to either get approval from the original authors to license the code under less restrictive terms or, if not, to isolate the offending classes in a separate (optional) module?
This way using Objenesis would be much more convenient for the many Eclipse projetcs to use ..

Regards,
Kai

@henri-tremblay
Copy link
Contributor

You guys have quite motivated lawyers. The copyright is from BEA which is now Oracle. The code was done by @mrbubble. I don't remember why the copyright was added.

But I think I will simplify and just remove this instantiator. It was used for a very old version of JRockit anyway so I don't think anybody will ever use it anymore.

@henri-tremblay henri-tremblay self-assigned this May 18, 2016
@henri-tremblay henri-tremblay added this to the 2.4 milestone May 18, 2016
@sophokles73
Copy link
Author

@henri-tremblay that sounds great :-) Thanks a lot! Any idea when you want to release 2.4?

@henri-tremblay
Copy link
Contributor

As soon as possible. Even if this is the only fix.

@sophokles73
Copy link
Author

Ok, thanks again. This will make our lives a lot easier :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants