Bug 997794
Summary: | Bad HornetQ version in console log | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Miroslav Novak <mnovak> |
Component: | Build, HornetQ | Assignee: | Paul Gier <pgier> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kremensky <pkremens> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1.1 | CC: | ataylor, csuconic, msvehla, myarboro |
Target Milestone: | ER7 | Keywords: | Regression |
Target Release: | EAP 6.1.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-16 20:29:25 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Miroslav Novak
2013-08-16 08:36:01 UTC
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: ./modules/system/layers/base/org/hornetq/main/hornetq-commons-2.3.5.Final.jar ./modules/system/layers/base/org/hornetq/main/hornetq-core-client-2.3.5.Final.jar ./modules/system/layers/base/org/hornetq/main/hornetq-jms-client-2.3.5.Final.jar ./modules/system/layers/base/org/hornetq/main/hornetq-jms-server-2.3.5.Final.jar ./modules/system/layers/base/org/hornetq/main/hornetq-journal-2.3.5.Final.jar ./modules/system/layers/base/org/hornetq/main/hornetq-server-2.3.5.Final.jar ./modules/system/layers/base/org/hornetq/ra/main/hornetq-ra-2.3.5.Final.jar 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
cd hornetq-upstream
git tag | grep 2.3.5
>>> HornetQ_2_3_5_Final
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! |