[jakarta.ee-spec.committee] Are we changing GAVs for non-jakarta.* proje

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

[jakarta.ee-spec.committee] Are we changing GAVs for non-jakarta.* projects this release

From: Scott Stark <sstark@xxxxxxxxxx>
Date: Fri, 19 Jul 2019 11:19:44 -0700
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>

Apart from some project not using existing jakarta.* groupId based dependencies, I think that the only spec project without a jakarta.* groupId is javax.inject:javax.inject

Are we going to be changing its groupId in this release once it is forked?

Follow-Ups:
- Re: [jakarta.ee-spec.committee] Are we changing GAVs for non-jakarta.* projects this release
  - From: Bill Shannon

Prev by Date: [jakarta.ee-spec.committee] Update dependencies to use the jakarta.* groupId releases
Next by Date: Re: [jakarta.ee-spec.committee] Are we changing GAVs for non-jakarta.* projects this release
Previous by thread: [jakarta.ee-spec.committee] Update dependencies to use the jakarta.* groupId releases
Next by thread: Re: [jakarta.ee-spec.committee] Are we changing GAVs for non-jakarta.* projects this release
Index(es):
- Date
- Thread

Breadcrumbs