[jakarta.ee-spec.committee] Issue with dependencies

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

[jakarta.ee-spec.committee] Issue with dependencies

From: Scott Stark <sstark@xxxxxxxxxx>
Date: Mon, 15 Jul 2019 08:03:48 -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>

In a discussion with Arjan and Dmitry today about the TCK jobs, it came up that specs have dependencies that are not available in staging as yet, so they cannot really do the final staging release. I guess that is why we have the schedule broken up into a phase where individual specs pass the TCK without updating dependencies in their pom, and once all specs have done that and are staged, the “Make API staging releases” step entails restating API jars with updated dependencies in their pom files?

Are we expecting that the TCK jobs are re-run and the release review PRs updated?

Follow-Ups:
- Re: [jakarta.ee-spec.committee] Issue with dependencies
  - From: Kevin Sutter

Prev by Date: [jakarta.ee-spec.committee] Reminder: Jakarta EE Update call - Wednesday, July 17, 2019 @11 AM EST
Next by Date: Re: [jakarta.ee-spec.committee] Issue with dependencies
Previous by thread: [jakarta.ee-spec.committee] Reminder: Jakarta EE Update call - Wednesday, July 17, 2019 @11 AM EST
Next by thread: Re: [jakarta.ee-spec.committee] Issue with dependencies
Index(es):
- Date
- Thread

Breadcrumbs