Using Caciocavallo code

[Glen Schrader (gschrader)]

> On Sep 30, 2019, at 5:40 AM, Mario Torre <neugens.limasoftware at gmail.com> wrote:
> 
> 
> I think the mailing list is only really significant if you want to use
> it for reviews (which is where Skara would help, since it makes the
> bridge between GitHub and the mailing list automatic). As for the bug
> database, historically Cacio predates the public Jira OpenJDK, so we
> always used our own bugzilla:
> 
> https://icedtea.classpath.org/bugzilla/describecomponents.cgi?product=Caciocavallo
> 
> I would be happy to hand you the "keys”.


I only spot, 7 issues in there (4 without resolution) so maybe just manually copying them into GitHub Issues is the easiest.


> 
> I didn't, and I don't think Roman did either, we should probably
> contact GitHub and see who owns that and if they are willing to
> release it.

I sent GitHub a request, we’ll see what they say.



> 
> I don't think there's any problem in changing it, although for
> historical reasons we may want to keep it the same. If you refactor
> the group id you should also change the packages though, for
> consistency.
> 

Given Dalibor’s comment, I guess changing it probably makes more sense. How about the copyright notices, I noticed there is a mix between Sun and Oracle and even a couple Red Hat notices thrown in. I assume those remain unchanged? What about current files that are missing one, should one be added?

Thanks,
Glen