[ee4j-build] jaxrpc-ri appears to be stored incorrectly in staging

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

[ee4j-build] jaxrpc-ri appears to be stored incorrectly in staging

From: Jim Krueger <jckofbyron@xxxxxxxxx>
Date: Tue, 27 Nov 2018 12:18:21 -0600
Delivered-to: ee4j-build@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/ee4j-build>
List-help: <mailto:ee4j-build-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/ee4j-build>, <mailto:ee4j-build-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/ee4j-build>, <mailto:ee4j-build-request@eclipse.org?subject=unsubscribe>

While doing some pre-release checking this morning I discovered that an rc-list of jakartaxmlrpc projects using the jakartaee-stable-bot credentials lists the following:

[INFO] jakartaxmlrpc-1000   CLOSED   jakarta.xml.rpc:jakarta.xml.rpc-api:1.1.3
[INFO] jakartaxmlrpc-1001   CLOSED   jakarta.xml.rpc:jakarta.xml.rpc-parent:1.1.5

jakarta.xml.rpc-api:1.1.3 is should be there. However jakarta.xml.rpc-parent:1.1.5 should not since it is the RI (https://github.com/eclipse-ee4j/jax-rpc-ri/blob/master/jaxrpc-ri) .

This project should be associated with Metro not Stable.

I'm not exactly sure how this happened or what needs to be done to resolve it. However, I do not thing that I will be able to release the jakartaee-stable projects until this is resolved. Perhaps there is an issue with the credentials?

Thanks,

Follow-Ups:
- Re: [ee4j-build] jaxrpc-ri appears to be stored incorrectly in staging
  - From: Romain Grecourt

Prev by Date: Re: [ee4j-build] Issue with Jakartaee-stable project release
Next by Date: Re: [ee4j-build] jaxrpc-ri appears to be stored incorrectly in staging
Previous by thread: [ee4j-build] Issue with Jakartaee-stable project release
Next by thread: Re: [ee4j-build] jaxrpc-ri appears to be stored incorrectly in staging
Index(es):
- Date
- Thread

Breadcrumbs