Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] [data-dev] Why repo name different from all others at jakartaee?
Hi,

This was brought up in the CDI group as well. After some discussion it appeared there's no real reason for the difference. People sometimes just arbitrary pick a name or an approach and don't look at any of the existing names. Of course there's the historical aspect as well and the desire to keep history. We talked about merging the CDI repos, which is a bit more work since history has to be preserved.

Kind regards,
Arjan Tijms


On Mon, Sep 5, 2022 at 3:07 PM Werner Keil <werner.keil@xxxxxxx> wrote:

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
Gesendet: Montag, 5. September 2022 14:36
An: data developer discussions
Betreff: Re: [data-dev] Why repo name different from all others at jakartaee?

 

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
Gesendet: Montag, 5. September 2022 14:08
An: data developer discussions
Betreff: Re: [data-dev] Why repo name different from all others at jakartaee?

 

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:

Why was „data“ called „data-api“ again while every other Jakarta EE repository has „api“ underneath as a folder:

https://github.com/jakartaee/security

https://github.com/jakartaee/servlet

…

 

Why was there an exception for Jakarta Data?

 

Maybe there was a misunderstanding between Otavio and Ivar, because I heard in the call something about the TCK being separate, but that still means API and Spec are under that repository just like all the others and „data-api/api“ plus „data-api/spec“ just sound weird.

 

Or is the plan to have „data-api“ and a separate „data-spec“ repo here?

 

Thanks,

Werner

_______________________________________________
data-dev mailing list
data-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org


 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

 

 

_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec

Back to the top