Description of problem: When migrating [BRL] asset inside the JCR repository, following exception is thrown: java.lang.IncompatibleClassChangeError at org.drools.xml.SemanticModules.addSemanticModule(SemanticModules.java:31) at org.drools.compiler.PackageBuilderConfiguration.addSemanticModule(PackageBuilderConfiguration.java:376) at org.drools.guvnor.server.builder.BRMSPackageBuilder.getPackageBuilderConfiguration(BRMSPackageBuilder.java:137) at org.drools.guvnor.server.builder.BRMSPackageBuilder.<init>(BRMSPackageBuilder.java:67) at org.drools.workbench.jcr2vfsmigration.migrater.asset.GuidedEditorMigrater.migrate(GuidedEditorMigrater.java:98) at org.drools.workbench.jcr2vfsmigration.migrater.asset.GuidedEditorMigrater$Proxy$_$$_WeldClientProxy.migrate(GuidedEditorMigrater$Proxy$_$$_WeldClientProxy.java) at org.drools.workbench.jcr2vfsmigration.migrater.AssetMigrater.migrate(AssetMigrater.java:174) at org.drools.workbench.jcr2vfsmigration.migrater.AssetMigrater.migrateAll(AssetMigrater.java:144) at org.drools.workbench.jcr2vfsmigration.migrater.AssetMigrater$Proxy$_$$_WeldClientProxy.migrateAll(AssetMigrater$Proxy$_$$_WeldClientProxy.java) at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrater.migrateAll(Jcr2VfsMigrater.java:91) at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrater$Proxy$_$$_WeldClientProxy.migrateAll(Jcr2VfsMigrater$Proxy$_$$_WeldClientProxy.java) at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrationApp.migrate(Jcr2VfsMigrationApp.java:64) at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrationApp.run(Jcr2VfsMigrationApp.java:52) at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrationApp.main(Jcr2VfsMigrationApp.java:37) Version-Release number of selected component (if applicable): 6.0.0-ER5 How reproducible: Always Steps to Reproduce: 1. Download migration tool from http://dev138.mw.lab.eng.bos.redhat.com/candidate/brms-6.0.0-ER5/jboss-bpms-brms-6.0.0-redhat-5-migration-tool.zip 2. Download the attached jcr repository (contains BRL that will reproduce the issue) and unzip it. 3. Run the ./runMigration.sh from "bin" dir and point it to the above mentioned jcr repo. Actual results: java.lang.IncompatibleClassChangeError thrown. Expected results: Migration ends successfully. Additional info:
Created attachment 829423 [details] JCR repo that will reproduce the issue.
It seems related to the release version. At community works fine, so I expect the issue to be fiexed with next prod.build (probably with ER6). For now the testing is done with the community. If at next build the problem persists, this bugzilla it would have to reopen. I reassign the BZ to Petr Siroky, to reopen it if necessary.
Just tested with ER6, issue is still there. I think it is indeed introduced during productization as the the contents of 'libs' dir differs in community and in product. For example the lucene version in community is 2.4.1, but in product it's 4.0.0 which makes the tool unusable as Jackrabbit can not really work with that lucene version (it needs the 2.4.x). There are also other jars that are either missing in product or should not be there. Maybe the assembly file is different? Or could this be related to the different dependency management in community and product?
Verified fixed in 6.0.0-ER7.