Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Question about forking the TCK Signature test library
Thanks Emily!


On Mon, Jan 22, 2024 at 5:01 AM Emily Jiang via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:


On Sat, Jan 20, 2024 at 5:59 PM Scott Stark via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:
So a potential problem with the project is that it uses the GPL v2 license:

The output of sigtest is not GPL, so there is no problem with using it, but in terms of bringing such code into an EF repo, I don't know what the restrictions are. I'll raise an issue with the EF on such code usage. Perhaps it needs to be forked into another org like https://github.com/jakartaredhat and released as an independent tool if it cannot be incorporated into the jakartaee-tck-tools repo. I'm going to do such a fork as I need an update for the Jakarta Validation TCK work that is ongoing.

I checked the permitted license page under EF here. GPL v2 was not listed there. I have cc-ed license@xxxxxxxxxxx to see how best to proceed with this.
Thanks
Emily

On Fri, Jan 19, 2024 at 2:29 PM Scott Marlow via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:
From the responses, forking the netbeans-apitest library into the https://github.com/eclipse-ee4j/jakartaee-tck-tools repo is the best option to take for our near term needs.  

On Thu, Jan 11, 2024 at 2:08 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
Thanks Kyle Aure for raising the $subject in [1] which I am echoing here.  Kyle asked on [1]:
"
Since this library [2]  is so integral to Jakarta EE TCK testing should eclipse manage a fork of this project so we can make these kind of changes? The base project doesn't seem to accept issues :(
"

The [2] netbeans-apitest library is used for our TCK signature testing which we use to record Specification API jar contents and to verify that Specification implementations use the correct classes and no more or less than the correct classes.  We also ensure that SPEC API implementations are not super-setted (e.g. no additional public fields/methods/annotations are added to implementations) and that SPEC API implementations are not sub-setted (e.g. no expected public fields/methods/annotations are removed from implementations).  The no super/sub setting is to prevent fragmentation of the Jakarta EE space as was experienced previously with Unix ports.

For background, the netbeans-apitest library [2] is based on the OpenJDK sigtest library [3] which is now archived (I'm not sure if that was forked to a different location).

Should we fork the netbeans-apitest library [2] to somewhere that is not a personal github repo?  If yes, where should it be moved to?  Some possible options:

1.  Fork [2] to a new repository under https://github.com/jakartaee 
2.  Fork [2] to be maintained as part of https://github.com/eclipse-ee4j/jakartaee-tck-tools
3.  Fork [2] to be in some other toplevel (e.g. not Eclipse) repository.

Thoughts?

Scott

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev


--
Thanks
Emily

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top