Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1059441

Summary: Jcr2vfs migration tool generates incorrect WorkItemDefinitions
Product: [Retired] JBoss BRMS Platform 6 Reporter: jbride <jbride>
Component: Migration ToolAssignee: Neus Miras <nmirasch>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Široký <psiroky>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: kverlaen, lpetrovi, psiroky, rrajasek, vigoyal
Target Milestone: ER1   
Target Release: 6.0.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The jcr2vfs migration tool generates workitemdefinition files with invalid import statements. The import statements refer to package names that are not valid and therefore the resultant files cannnot be used. Cause: Consequence: Fix: Result:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 19:57:44 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 jbride@redhat.com 2014-01-29 21:21:09 UTC
Hi.
  As of CR2, the jcr2vfs migration tool generates workitemdefinition files whose import statements are not correct.  In particular, the migration tool adds the following to a wid :

import org.drools.process.core.datatype.impl.type.ObjectDataType;
import org.drools.process.core.datatype.impl.type.StringDataType;


the correct package names should be:

import org.drools.core.process.core.datatype.impl.type.StringDataType;
import org.drools.core.process.core.datatype.impl.type.ObjectDataType


thanks!  jeff

Comment 2 Neus Miras 2014-02-03 17:10:57 UTC
It was fixed when the https://bugzilla.redhat.com/show_bug.cgi?id=1038216 was resolved.

Comment 3 Neus Miras 2014-02-05 14:21:04 UTC
Ajustment related with the asset migration

6.0.x
https://github.com/droolsjbpm/drools-wb/commit/4479da25ae1dc53d1ff9f73bcbdf3f07197670a4

Comment 4 Petr Široký 2014-02-20 16:56:27 UTC
Verified fixed in 6.0.1-ER1.