Re: [openmq-dev] [jms-dev] Keeping Open MQ in Sync with Message/JMS bund

[David Blevins <dblevins@xxxxxxxxxxxxx>]

> On Sep 29, 2020, at 6:14 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
> 
>> On Sep 28, 2020, at 8:25 AM, Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:
>> 
>> Do we have a mechanism to keep the Eclipse JMS Messaging jars in sync. with Open MQ? Once the JMS/Messaging API is finished, we will need to integrate those JAR bundles into Open MQ. Then, Open MQ will need to be integrated into Eclipse GlassFish. I don't know if OSGi work is also needed, but that is also sometimes neglected with Eclipse GlassFish.
>> 
>> Are there issues tracking these requirements? Should I create?
> 
> I'm not sure either -- I'll default to OpenMQ committers for that guidance.
> 
> I just promoted the Messaging TCK:
> 
> - https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee9-eftl/promoted/jakarta-messaging-tck-3.0.0.zip
>   sha256: a73f36b91113002a2923612a54323bde17d0ea1f43f48f5a1dbe0301eb7b2035
> 
> Staged API binaries are here:
> 
> - https://jakarta.oss.sonatype.org/content/groups/staging/jakarta/jms/jakarta.jms-api/3.0.0/
> 
> Next step is for us to get a released OpenMQ that passes the above TCK without modifications such as overwriting API jars after unzipping. Once that is done and we have a certification request, we can put the Messaging spec up for final ballot.
> 
> I'm not sure what the status is on the last release of OpenMQ.  If it can pass the above TCK unmodified, it will work for the vote.  We would still need another TCK run with a modified version that uses the staged API jar just to verify the API jar, but that's completely separate from the certification request and wouldn't require another release (assuming we already have one that can pass the promoted TCK).
> 
> Timeline wise, do we think we can have a certification request by end of day Thursday so we can go to final ballot Friday?

Any OpenMQ committers who can help with the above?


-David