| Re: [jakarta.ee-spec] [data-dev] Why repo name different from all others at jakartaee? |
There actually is at least one case where: https://github.com/jakartaee/validation https://github.com/jakartaee/validation-spec exist. Maybe we did not discuss it long enough in the Spec Committee, because IMO above example makes perfect sense to have https://github.com/jakartaee/validation-api https://github.com/jakartaee/validation-spec instead, but for projects that combine spec and API Maybe the „-api“ should be optional, which the side-note also permits ;-) Which is why in the current layout unless Jakarta Data went to split the „spec“ part into its own repo „data“ feels better. Werner Von: Werner Keil Ok, thanks for the pointer, guess then others like „security“ will have to change their names soon? Although the sentence As noted above, separate repositories for API and TCK is the typical layout. Specification projects are free to organize their specification, API and TCK how they see fit as long as all repositories start with the short name of the related specification. Puts the whole naming convention in limbo again if projects can also deviate from it? Werner Von: Ivar Grimstad It is according to the naming standard being put forward by the Spec Committee. Ivar On Mon, Sep 5, 2022 at 1:57 PM Werner Keil <werner.keil@xxxxxxx> wrote:
-- Ivar Grimstad Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. |