Bug 777727 (SOA-243) - request for mvel library update
Summary: request for mvel library update
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-243
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBoss Rules
Version: 4.2 IR8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 Beta 1
Assignee: Mike Brock
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks: SOA-45
TreeView+ depends on / blocked
 
Reported: 2007-12-18 10:41 UTC by Jaroslaw Kijanowski
Modified: 2013-06-17 05:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-17 14:51:49 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-243 0 None None None Never

Description Jaroslaw Kijanowski 2007-12-18 10:41:36 UTC
Date of First Response: 2007-12-19 00:14:45
project_key: SOA

The mvel library is located in deploy/jbossesb.sar/lib

Some drools tests are failing because they depend on the newest mvel version. Can we provide mvel14-1.2.8.jar?

Comment 1 Jaroslaw Kijanowski 2007-12-18 10:42:04 UTC
Link: Added: This issue is a dependency of SOA-45


Comment 2 Mike Brock 2007-12-19 05:14:45 UTC
updated as part of the SOA build.  Drools is also updated.

Comment 3 Jaroslaw Kijanowski 2007-12-19 19:03:32 UTC
downloaded both, soa-p and standalone from http://porkchop.redhat.com/devel/candidates/SOAP4.2.0/IR9/soa-4.2.0.IR9.zip and http://porkchop.redhat.com/devel/candidates/SOAP4.2.0/IR9/standalone-soa-4.2.0.IR9.zip.

Both have old mvel:

mvel14-1.2rc4rv908.jar

Comment 4 Jaroslaw Kijanowski 2008-01-17 14:06:07 UTC
now we need mvel 1.2.21

Comment 5 Mike Brock 2008-01-17 14:51:17 UTC
please re-open new issues.

Comment 6 Mark Little 2008-01-17 14:52:47 UTC
Jaroslaw, please do not reuse issues unless they were not resolved correctly. This one was closed with the right version of MVEL at the time. Create a new issue: they are cheap!


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