Hi all, When I was creating a custom product using carbon-kernel version 5.2.0-alpha[1] the following issue aroused. In a scenario where a product is build with 2 runtimes called runtimeA and runtimeB.
runtimeA contains the below feature among it's other features pax.exam.feature v5.2.0.0 sample-bundle2 v5.2.0.0 log-bundle v1.5.0 while runtmeB contains the below feature among it's other features sample.feature v5.2.0.1 sample-bundle1 v5.2.0.0 monitor-bundle v1.5.0 pax.exam.feature v5.2.0.1 As shown above since there is a dependency to the `pax.exam.feature,v5.2.0.1` from the `sample.feature,v5.2.0.1`, to have both versions of `pax.exam.feature` to be installed into the separate runtimes of the product, it is required to define dependency information of each `pax.exam.feature` versions (v5.2.0.0 and v5.2.0.1) under the <dependencies> tag in the pom.xml file. But during the build process, maven will only pick one version of that dependency and omit the other versions to avoid any conflicts using the *"nearest in the dependency tree"* strategy (already asked in stackoverflow [1]). This will results in a build failure as if the build process resolves dependency of `pax.exam.feature` v5.2.0.0`, the version v5.2.0.1 will not be available during build and vice versa. Is this a legitimate case that we should address? IMO it will be a best practise to use the newest versions of the features available when creating runtimes than using the older versions which in turn will resolve this issue. Your comments are highly appreciated. [1] https://github.com/wso2/carbon-kernel/tree/v5.2.0-alpha [2] https://stackoverflow.com/questions/24962607/multiple-versions-of-the-same-dependency-in-maven Thanks -- *Regards,* *Kasun Siyambalapitiya* *Software Engineer* WSO2 Inc. - http://wso2.com/ lean . enterprise . middleware Tel : 0715523466 E mail : kasu...@wso2.com Blog: https://medium.com/@kasunsiyambalapitiya <https://wso2.com/signature>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
