| 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 |
Hi,
Probably best to not let the /api module of messages depend on the parent to begin with.
It should be changed here: https://github.com/jakartaee/messaging/blob/master/api/pom.xml#L24
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
Kind regards,Arjan
On Mon, Feb 28, 2022 at 6:06 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
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