[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jakarta.ee-spec.committee] Incremental vs Big Bang boms
|
Another question is how would we envision a profile bom to be defined in an incremental vs Big Bang approach. The incremental approach seems straightforward, there is a mix of javax and jakarta based artifacts depending on what has been updated.
The Big Bang bom leaves a question of what should be in it. Consider a Jakarta EE 9 Big Bang release where only the REST spec has been updated, but all apis now are under the jakarta.* namespace. Greenfield development would only use jakarta.* based classes and would work with a bom that only included those artifacts.
If I have a Jakarta EE 8 app that is updated to use the new REST apis, it would need to include both Jakarta EE 8 and Jakarta EE 9 boms to compile the app. Do we envision having a compatibly bom such that there is a single bom a user could use to still build from source against? The concern here is that they intended to update all REST api usage to the Jakarta EE 9 apis, but missed some locations. If they have to include both Jakarta EE 8 and Jakarta EE 9 boms, this would be masked. If there was a Jakarta EE 9 compatibility bom, compiling against it would fail on the locations that did not update from JAX-RS to the Jakarta EE 9 REST apis.
