Created attachment 941492 [details] switchyard-bpm log ===Description of problem: Some switchyard features cannot be installed on karaf without having previously installed switchyard feature. switchyard-bpm switchyard-hibernate => switchyard-2.0.0.Alpha2-redhat-1-core-features.xml should be fixed === Version-Release number of selected component (if applicable): FSW 6.1 DR2 === How reproducible: === Steps to Reproduce: features:addurl mvn:org.switchyard.karaf/switchyard/2.0.0.Alpha2-redhat-1/xml/features features:install switchyard-bpm === Additional info: Prerequisite: features:install switchyard
Please use the following features url when working with Fuse: features:addurl mvn:org.switchyard.karaf/switchyard/2.0.0.Alpha2-redhat-1/xml/core-features Notice the classifier is "core-features" instead of "features".
Rob, why should I use classifier "core-features"? File with classifier "features" contains the following content and "core-features" is contained. <repository>mvn:org.switchyard.karaf/switchyard/2.0.0.Alpha2-redhat-1/xml/core-features</repository> <repository>mvn:org.apache.camel.karaf/apache-camel/2.12.0.redhat-610379/xml/features</repository> <repository>mvn:org.apache.cxf.karaf/apache-cxf/2.7.11/xml/features</repository> <repository>mvn:org.apache.activemq/activemq-karaf/5.9.0/xml/features</repository> Nevertheless I tried to reproduce the bug with the following features url and the problem still exists. mvn:org.switchyard.karaf/switchyard/2.0.0.Alpha2-redhat-1/xml/core-features
Hey Martin, The reason for the two different files is because those repository declarations cause the dependencies to be resolved from them, as opposed to the repositories configured on Fuse. For example, the activemq repo will pull in v5.9.0, instead of 5.9.0.redhat-600379, which is what is packaged with Fuse. Same goes for CXF. It looks like prod has overwritten the version of Camel so it matches what Fuse is using, so that takes care of one of the problems. Long story short, core-features only includes the SwitchYard features and repository declarations for SwitchYard specific dependencies (e.g. drools). As this works with the community builds, I suspect the cause lies in something that changed as part of productization. Thanks for verifying. Rob
Hey David, could you please verify this is working correctly as part of testing your current changes (upgrade to 6.2)? It looks like much has changed between Alpha2 and Alpha3. Thanks in advance.
Rob Cernich <rcernich> updated the status of jira SWITCHYARD-2358 to Resolved