[jakarta.ee-spec.committee] Updating spec APIs (avoid jms, ejb, jws, etc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jakarta.ee-spec.committee] Updating spec APIs (avoid jms, ejb, jws, etc)

From: Jean-Louis Monteiro <jlmonteiro@xxxxxxxxxxxxx>
Date: Tue, 12 Apr 2022 17:34:33 +0200
Delivered-to: jakarta.ee-spec.committee@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jakarta.ee-spec.committee/>
List-help: <mailto:jakarta.ee-spec.committee-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee>, <mailto:jakarta.ee-spec.committee-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jakarta.ee-spec.committee>, <mailto:jakarta.ee-spec.committee-request@eclipse.org?subject=unsubscribe>

Hi,

I was reviewing the Messaging PR to put a ballot up and realized that it's still using jms-api instead of messaging-api. Though it does not appear to be a blocker, we should prioritize and ask the projects to be all using the list of names we agreed on.

After checking quickly with Ivar, looks like jms, jws, ejb, ws.rs are all still using old naming

Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

Follow-Ups:
- Re: [jakarta.ee-spec.committee] Updating spec APIs (avoid jms, ejb, jws, etc)
  - From: Paul Buck

Prev by Date: Re: [jakarta.ee-spec.committee] Requirements for individual specification TCKs
Next by Date: Re: [jakarta.ee-spec.committee] Updating spec APIs (avoid jms, ejb, jws, etc)
Previous by thread: [jakarta.ee-spec.committee] TCK promotion CI job?
Next by thread: Re: [jakarta.ee-spec.committee] Updating spec APIs (avoid jms, ejb, jws, etc)
Index(es):
- Date
- Thread

Breadcrumbs