Using Caciocavallo code

[Emilian Bold]

The mailing list still seems to work.

Making a public GitHub repository should be enough.

PS: for internal projects GPL does not force you to make the code public,
but don't let that stop you!

--emi

sâm., 28 sept. 2019, 02:55 Glen Schrader (gschrader) <gschrader at gmail.com>
a scris:

> Hello again,
>
> I know the project was dissolved (in fact I’m not even sure this email
> will go through) but I’m just wondering what I should do with code changes
> I made in order to get the shared and tta modules working under JDK11. My
> initial plan was to stop using Caciocavallo and use Xvfb/vnc to run
> headless unit tests but I ran into other issues going that route so I ended
> up making the necessary code changes. I know the license is GPL so I should
> be making the code available, right now I have it imported into a private
> GitHub repo, so at the very least I will make that public but I wonder if
> I should just take the code I need and start a new project. Any thoughts?
>
> PS if this email bounces, then I will email Mario and Roman directly
> instead.
>
> Thanks,
> Glen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20190928/45870c1d/attachment.html>