Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] CQs for ATO for Jersey

Hi,

My understanding would be that from a legal point of view the CQs are not needed if we are talking about about Eclipse projects. 

But if Jersey itself does not publish the artifacts as OSGi bundles in a p2 repository, they are still needed in Orbit where they are consumable by Eclipse projects that rely on p2.

Greez, 
Dirk 

Jonah Graham <jonah@xxxxxxxxxxxxxxxx> schrieb am Fr., 14. Feb. 2020, 03:32:
Hello fellow Orbiters and Tony (Tony explicitly on CC list as I don't know if you subscribe to included lists).

Apologies if I have missed some communications about this.

I was just working through approving the Orbit CQs. #21655 to 21663 all deal with adding Version 2.30 of Jersey to Orbit (Jersey has many parts). However Jersey is now an Eclipse project so it seems that including Jersey in Orbit and creating CQs for it does not make sense to me. 

Should Jersey be removed from Orbit and dependent projects point to Jersey directly? Should Jersey officially join release train as org.glassfish.jersey is part of the current simrel?

AFAICT the complication here is that the Orbit build process turns the maven artifacts into OSGi bundles. The gerrit that Tony has been working on is https://git.eclipse.org/r/#/c/156836/ for this.

Thanks for your input,
Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com 
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/orbit-dev

Back to the top