Re: [DISCUSS] JakartaEE - continue rolling our own API jars vs use official ones?

As someone who has fought for better OSGi support in the MP spec APIs I can say that this has proven difficult and largely without success. Le sam. 25 avr. 2020 à 10:43, Mark Struberg a écrit : > JakartaEE moved to the Eclipse Foundation and all the APIs are now >> available without much restric

Re: [DISCUSS] JakartaEE - continue rolling our own API jars vs use official ones?

The fact we sometimes change the default provider can justify we keep it. That said we must also provide the module-info file to stay compliant - and not an automatic module name. The copyright is also a nice to have which enforces this. Finally I agree keeping osgi control is important for us an

[DISCUSS] JakartaEE - continue rolling our own API jars vs use official ones?

Hi folks! JakartaEE moved to the Eclipse Foundation and all the APIs are now available without much restrictions. There are 4 potentially problematic issues with the 'official' spec APIs: 1.) Most of them are EPLv2 licensed. This is a catB license [1] and weak-copyleft. That means we MUST add a

Re: Thinking to release geronimo-config-1.2.3

no, go on! Anything missing? LieGrue, strub > Am 12.04.2020 um 21:23 schrieb Raymond Auge : > > This would be 1.2.3 with support for MP-Config 1.4 final. > > Any objections? > -- > Raymond Augé (@rotty3000) > Senior Software Architect Liferay