Bug 1267383 - JDG 6.5.1 GA JAR files emit a version of 6.3.1.CR1-redhat-1
Summary: JDG 6.5.1 GA JAR files emit a version of 6.3.1.CR1-redhat-1
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Build
Version: 6.5.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: CR1
: 6.6.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-29 21:01 UTC by Alan Field
Modified: 2023-05-31 23:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alan Field 2015-09-29 21:01:57 UTC
Description of problem:

The infinispan-core-6.3.1.Final-redhat-1.jar file includes the following code in the org.infinispan.Version.java file:

   private static final String MAJOR = "6";
   private static final String MINOR = "3";
   private static final String MICRO = "1";
   private static final String MODIFIER = "CR1-redhat-1";

And this version is logged as "6.3.1.CR1-redhat-1". The embedded uberjar returns the same:

[afield@dhcp65-183 jboss-datagrid-6.5.1-library]$ java -cp ./infinispan-embedded-6.3.1.Final-redhat-1.jar org.infinispan.Version
Infinispan

Version: 	6.3.1.CR1-redhat-1
Codename: 	Infinium
History: 	(see https://jira.jboss.org/jira/browse/ISPN for details)

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Martin Gencur 2015-12-17 13:07:31 UTC
This cannot be verified with ER build. The fix is only activated with CR builds. Moving target to CR1.

Comment 5 Martin Gencur 2016-01-11 13:03:32 UTC
Verified for both:
1) server distribution - by starting the server
2) library distribution - by running the following command with the library mode uberjar: java -cp ./infinispan-embedded-6.4.0.Final-redhat-1.jar org.infinispan.Version


Note You need to log in before you can comment on or make changes to this bug.