Bug 1006467

Summary: Revert version and group for batik to 1.6
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Gary Brown <gbrown>
Component: BPEL IntegrationAssignee: Gary Brown <gbrown>
Status: CLOSED WONTFIX QA Contact: Jiri Sedlacek <jsedlace>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: atangrin, ldimaggi, oskutka, soa-p-jira
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-31 15:41:55 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 Gary Brown 2013-09-10 16:32:58 UTC
Description of problem:

jBPM team are unable to upgrade to version 1.7, so to ensure consistent version of batik we need to revert the version used by riftsaw to 1.6 (and the associated change in GAV group).

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Gary Brown 2013-09-16 15:59:22 UTC
Unfortunately when I tried to revert the batik version to 1.6, the batik-codec and batik-anim dependencies could not be resolved from Nexus.

Not sure how they were resolved before. I tried commenting them out, and it builds fine, but causes class not found exceptions when attempting to render the svg diagram.

Have informed Kris - but not sure how to proceed with this issue, as it looks like riftsaw has problems moving back, and jBPM have problems upgrading to version 1.7.

Comment 3 JBoss JIRA Server 2013-10-31 16:18:09 UTC
Gary Brown <gary> updated the status of jira SWITCHYARD-1693 to Closed

Comment 4 JBoss JIRA Server 2013-10-31 16:18:09 UTC
Gary Brown <gary> made a comment on jira SWITCHYARD-1693

As this downgrading the version is problematic, this issue is being closed and will remain on version 1.7.