Bug 726597 - BRMS jars improperly named
Summary: BRMS jars improperly named
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Build Process
Version: BRMS 5.2.0-ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: BRMS 5.2.0.GA
Assignee: Ryan Zhang
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-29 07:33 UTC by Lukáš Petrovický
Modified: 2014-10-27 01:14 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Lukáš Petrovický 2011-07-29 07:33:33 UTC 
Drools JAR files in BRMS have the wrong suffix. Instead of being named "drools-something-5.2.0.BRMS.jar", they are named "drools-something-5.2.1.BRMS.jar"

It was agreed this week with John Graham that it should be reverted back to 5.2.0.BRMS.
Comment 1 Ryan Zhang 2011-08-16 11:27:51 UTC 
This would be easy to fix.

Just to want to confirm, we have added "-ER2" ... suffix in the drools jars version in order to avoiding version overlapping  in MEAD env. So the "-ER/CR“ suffix shall be ok , right?
Comment 2 Lukáš Petrovický 2011-08-16 11:55:18 UTC 
I think that should be no problem at all.
Comment 3 Lukáš Petrovický 2011-08-20 13:34:39 UTC 
Also please make sure that the jBPM JARs have a proper suffix. (Currently they're suffixed with "SOA".)
Comment 4 Lukáš Petrovický 2011-08-26 12:12:52 UTC 
So far it looks good. I will wait for final verification once we get the CR bits.
Comment 5 Lukáš Petrovický 2011-08-28 11:57:49 UTC 
Just noticed that even with ER3, jBPM still has the "5.1.0" suffix - I think this needs to be changed to 5.2.0.
Comment 6 Ryan Zhang 2011-08-29 01:14:21 UTC 
OK, I would update jbpm to 5.2.0.BRMS too in next release. 
I had thought that it would be wise to follow the project's major version number.
Comment 7 Lukáš Petrovický 2011-09-19 12:28:23 UTC 
Verified in ER4
Note You need to log in before you can comment on or make changes to this bug.