I've restaged the API artifact without the parent dependency. I'll notify all other teams that depend on it.
Kind regards,
Ondrej Mihályi
Senior Payara Service Engineer
Payara - Supported Enterprise
Software for Jakarta EE and MicroProfile Applications
US: +1 415 523 0175 | UK: +44 207 754 0481
----------------------------------------------------------------------------------------------------------------------
Payara is a proud recipient of the prestigious
Queen's Award for Enterprise: International Trade 2021
Payara-Tech LDA, Registered Office: Rua Nova de São Pedro no. 54, 2nd floor, room “D”, 9000 048 Funchal, Ilha da Madeira, Portugal
VAT: PT 515158674 |
www.payara.fish |
info@xxxxxxxxxxx |
@Payara_Fish
From: messaging-dev <messaging-dev-bounces@xxxxxxxxxxx> on behalf of Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx>
Sent: 01 March 2022 15:05
To: EE4J Messaging project developer discussions <messaging-dev@xxxxxxxxxxx>; arjan tijms <arjan.tijms@xxxxxxxxx>
Cc: Gurunandan <gurunandan.rao@xxxxxxxxxx>
Subject: Re: [messaging-dev] Fwd: Missing org.eclipse.ee4j.jms:jms-parent:pom:3.1.0 when using staged jakarta.jms:jakarta.jms-api:3.1.0
OK, I'll try to stage a fixed version of the API and will let you know.
Kind regards,
Ondrej Mihályi
Senior Payara Service Engineer
Payara - Supported Enterprise
Software for Jakarta EE and MicroProfile Applications
US: +1 415 523 0175 | UK: +44 207 754 0481
----------------------------------------------------------------------------------------------------------------------
Payara is a proud recipient of the prestigious
Queen's Award for Enterprise: International Trade 2021
Payara-Tech LDA, Registered Office: Rua Nova de São Pedro no. 54, 2nd floor, room “D”, 9000 048 Funchal, Ilha da Madeira, Portugal
VAT: PT 515158674 |
www.payara.fish |
info@xxxxxxxxxxx |
@Payara_Fish
From: messaging-dev <messaging-dev-bounces@xxxxxxxxxxx> on behalf of Scott Marlow <smarlow@xxxxxxxxxx>
Sent: 28 February 2022 20:20
To: EE4J Messaging project developer discussions <messaging-dev@xxxxxxxxxxx>; arjan tijms <arjan.tijms@xxxxxxxxx>
Cc: Gurunandan <gurunandan.rao@xxxxxxxxxx>
Subject: Re: [messaging-dev] Fwd: Missing org.eclipse.ee4j.jms:jms-parent:pom:3.1.0 when using staged jakarta.jms:jakarta.jms-api:3.1.0
On 2/28/22 12:33 PM, arjan tijms wrote:
Hi,
Probably best to not let the /api module of messages depend on the parent to begin with.
https://github.com/jakartaee/messaging/pull/320 is a possible workaround. Staging the jms-parent from CI could also help, either solution likely requires running
some CI jobs. :-)
Thanks and kind regards,
Scott
Hi,
We are able to access the staged Messaging `3.1.0` SPEC API but not org.eclipse.ee4j.jms:jms-parent:pom:3.1.0:
"
Downloading from central:
https://repo.maven.apache.org/maven2/org/eclipse/ee4j/jms/jms-parent/3.1.0/jms-parent-3.1.0.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.727 s
[INFO] Finished at: 2022-02-28T11:45:30-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project dependency_copy: Could not resolve dependencies for project jakarta:dependency_copy:jar:1: Failed to collect dependencies at jakarta.jms:jakarta.jms-api:jar:3.1.0: Failed to read artifact descriptor for jakarta.jms:jakarta.jms-api:jar:3.1.0:
Could not find artifact org.eclipse.ee4j.jms:jms-parent:pom:3.1.0 in jakarta-staging (https://jakarta.oss.sonatype.org/content/repositories/staging/)
-> [Help 1]
"
Should org.eclipse.ee4j.jms:jms-parent:pom:3.1.0 be accessible?
Scott
_______________________________________________
messaging-dev mailing list
messaging-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://accounts.eclipse.org
_______________________________________________
messaging-dev mailing list
messaging-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
|