Red Hat Bugzilla – Bug 997794
Bad HornetQ version in console log
Last modified: 2015-02-20 06:32:19 EST
Description of problem:
In console log there is HornetQ version 2.3.5.Final:
09:45:23,920 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221001: HornetQ Server version 2.3.5.Final (Monster Bee, 123) [ce9bd290-0647-11e3-ba63-8d680f7503b8]
but in "hornetq" module ther are jars:
which are built from HornetQ tag "HornetQ_2_3_4_Final".
There is not tag HornetQ_2_3_5_Final in hornetq project  at this moment.
This issue was hit in EAP 6.1.1.ER6 but not in ER4 (ER5 rejected). Adding "Regression" keyword.
I would take this more seriously...
I just did a build using the EAP tag, and when I look at the modules, I see:
I bet there was a build issue and this took the previous version.
It seems some sort of mistake was made during the building and that kind of thing will differ between build and the actual tag.
I have no control over this since I don't own the build, you will have to check upstream on what happened.
I just did a fresh clone out of github:
git clone git://github.com/hornetq/hornetq.git hornetq-upstream
git tag | grep 2.3.5
so, the tag is there!
This is caused by the hard-coded version properties in the root POM.
Our build system automatically appends -redhat-X onto the end of the versions in the pom, however, it's not able to automatically update these properties.
For ER7 we can just hard code the correct version suffix, and then Clebert can try to find a way to automatically get the suffix from the pom version for the next release.
Upstream hornetq issue to track longer term fix: https://issues.jboss.org/browse/HORNETQ-1247
Good to see this fixed in EAP 6.1.1.ER7. Thanks!