Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-build] jaxrpc-ri appears to be stored incorrectly in staging
On 11/27/18 10:18 AM, Jim Krueger wrote:
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?
Why is jaxrpc-ri using jakarta as groupId ? Isn't the jakarta groupId/namespace only for APIs ?
Note that nexus permissions are mapped to groupIds, so that's why you are seeing both.

Thanks,

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build

Back to the top