search

eclipse-ee4j / openmq

OpenMQ
https://projects.eclipse.org/projects/ee4j.openmq/
Other
52 stars 34 forks source link

current imq client maven coordinates #520

Closed cachescrubber closed 1 year ago

cachescrubber commented 4 years ago

Sorry If this is a duplicate or RTFM but I could not find a current maven release for the openmq jms client. I use the following maven coordinates to pull in the openmq imq client 5.1 which dates back to 2014. mq-distribution seems under active development with regular releases.

      <dependency>
        <groupId>org.glassfish.mq</groupId>
        <artifactId>imq</artifactId>
        <version>5.1</version>
      </dependency>

What are the current maven coordinates for the imq client?

pdenis1 commented 3 years ago

bump

I can't seem to find version 6.0 in maven either. I've tried using org.glassfish.imq:imq:6.0 and also org.glassfish.mq:mq-distribution:6.0. I tried it like this also

implementation ("org.glassfish.mq:mq-distribution:6.0.0@pom") {
    transitive = true
}

but that only pulls down the pom file and no jar artifacts. Is it possible to include the mq client library in a gradle build or does it require some custom maven plugins? I'm using pure gradle and mavenCentral for dependencies .. not using maven plugins.

pzygielo commented 3 years ago

Currently only org.glassfish.mq:mq-distribution:6.2.0@zip is published to Central.

bvfalcon commented 2 years ago

Please publish into Maven Central or Jakarta Sonatype other dependencies. Very useful are mq-broker, mqjmsra-ra and many others.

pzygielo commented 2 years ago

SNAPSHOTs from current master (b7e25892e97435e687d7f5db338d0c7cce4e74b0) of mq-broker, mqjmsra-ra and many others are now available at https://jakarta.oss.sonatype.org/content/repositories/snapshots/org/glassfish/mq. They are not deployed continuously as for now. They are not deployed in release job as for now.

Please test.

bvfalcon commented 2 years ago

SNAPSHOTs ... are available at ...

Thanks a lot, this very helpful. I need release dependencies and have already found appropriated solution: Github Packages can be used as Maven repository.

But of course mq-distribution with zip-type artifact absolutely not enough. For example, I want to write test-module for Apache Camel using Open MQ instead of Active MQ. How can I do this with only zip-artifact? This is only one case, where Open MQ subsystems as maven dependencies can be used. They can be dozen for 10 minutes invented.

mheydem commented 1 year ago

My project depends on the imq.jar. Currently I see the following ugly workarounds:

and

Nobody can use the mq-distribution zip artifact directly. Please publish the release artifacts.

pzygielo commented 1 year ago

@mheydem - can you help and confirm that currently published artifacts (as snapshots so far, https://github.com/eclipse-ee4j/openmq/issues/520#issuecomment-1256517383) are usable in your project?

pzygielo commented 1 year ago

There is no plan to publish re-packaged lib/*.jars from distribution manually, so (most probably) there will be no org.glassfish.mq:imq anyway. Only existing maven modules.

mheydem commented 1 year ago

Thank you for explaining how the OpenMQ artifacts should be used. The mq-client artifact looks like it could be the right dependency. I replaced the dependency on imq with mq-client for testing purpose.

Unfortunately this can not be tested with my project, because it is based on:

The OpenMQ 6.4.0-SNAPSHOT artifacts currently

As soon as my project is sufficiently advanced in the migration with Jakarta and Java SE, this can be tested again.

cachescrubber commented 1 year ago

I just migrated my custom openmq-spring-boot-starter using the mq-client dependency.

Repository Setup

<repository>
  <id>jakarta-snapshots</id>
  <name>jakarta-snapshots</name>
  <url>https://jakarta.oss.sonatype.org/content/repositories/snapshots</url>
  <snapshots>
    <enabled>true</enabled>
  </snapshots>
  <releases>
    <enabled>false</enabled>
  </releases>
</repository>

Dependency Management

<dependency>
    <groupId>org.glassfish.mq</groupId>
    <artifactId>mq-client</artifactId>
    <version>6.4.0-SNAPSHOT</version>
</dependency>

Code compiles against spring-boot-3.0.0 parent / jdk17. I have yet to test a real JMS connection.

cachescrubber commented 1 year ago

Code compiles against spring-boot-3.0.0 parent / jdk17. I have yet to test a real JMS connection.

I can connect against a server running mq-5.1.

grmblfrz commented 1 year ago

Is there any chance of putting the current releases (6.0.0, 6.1.0, ... 6.3.0) or at least the latest mq-client to maven central? Snapshots are working for development but not really acceptable for releases imho.

cachescrubber commented 1 year ago

Hi @pzygielo.

Is there a release date planned for 6.4.0?

arjantijms commented 1 year ago

It's probably a good time for us to release a new version. There's quite an amount of changes between 6.3.0 and master:

What's Changed

pzygielo commented 1 year ago

I do agree that this might be time for 6.4.0.

I'd like to have this very one (more components in central) delivered too, but it requires updates on the Jenkins side. I can look at it probably in next week.

pzygielo commented 1 year ago

6.4.0-M1 is now staged for testing. This will not be pushed to central, but the final 6.4.0 will be very similar (if no issue is reported by the next Friday Feb 17th).

https://jakarta.oss.sonatype.org/content/repositories/staging/org/glassfish/mq/mq-client/6.4.0-M1/

cachescrubber commented 1 year ago

Thanks @pzygielo - I'll give it a try early next week.

pzygielo commented 1 year ago

Feel free to reply to https://www.eclipse.org/lists/openmq-dev/msg00240.html.

cachescrubber commented 1 year ago