On Sat, Dec 15, 2012 at 3:57 PM, Buddhika Chamith <[email protected]>wrote:
> There is no much point in installing BAM mediator feature on top of AS > since this is specific for ESB. Having said that the issue is some thing > that needs to be fixed if possible. > > This is not only specific to BAM mediator installation. mediation.initializer.server feature is going with many other features. So same conflicts can occur when trying to install those features which have dependency to mediation.initializer feature. The same problem is there with *identity.oauth.ui.*feature where it has external dependency features like webapp.mgt.server, jaxws.webapp.mgt.server included as part of it and not properly imported. These cause conflicts when installing features where P2 doesn't allow to update parts of features to newer versions. If every product is updated to use the same versions of features, this problem may not occur. However, some of our products are using older/newer versions of such conflicting features which are published in the p2-repo, hence this problem. Also some of the product categories in the p2-repo are still not updated to latest feature versions. If we are to fix this, need to change every conflicting features like identity.oauth.ui, mediation.initializer.server features to properly define feature imports to external dependencies. Changing these features can cause some product p2-profiles to break if they are not updated accordingly. We also have to make sure features and feature-categories in the p2-repo are updated to latest versions. How can we proceed with this? Thanks, Dileepa Regards > Buddhika > > On Sat, Dec 15, 2012 at 1:56 PM, Dileepa Jayakody <[email protected]>wrote: > >> Hi All, >> >> Getting below error when trying to install BAM Data Agents category from >> latest 4.0.5 p2-repo; >> >> Your original install request has been modified. >> org.wso2.carbon.databridge.datapublisher.feature.group-4.0.2 is already >> installed, so an update will be performed instead. >> >> Cannot complete the install because of a conflicting dependency. Software >> being installed: WSO2 Carbon - *BAM Mediator Aggregate Feature 4.0.5 >> (org.wso2.carbon.mediator.bam.feature.group 4.0.5)* Software currently >> installed: WSO2 Carbon - Event Server Feature 4.0.5 >> (org.wso2.carbon.event.server.feature.group 4.0.5) Only one of the >> following can be installed at once: WSO2 Carbon - Event Server Feature >> 4.0.2 (org.wso2.carbon.event.server.feature.jar 4.0.2) WSO2 Carbon - Event >> Server Feature 4.0.5 (org.wso2.carbon.event.server.feature.jar 4.0.5) >> Cannot satisfy dependency: From: WSO2 Carbon - Event Server Feature 4.0.2 >> (org.wso2.carbon.event.server.feature.group 4.0.2) To: >> org.wso2.carbon.event.server.feature.jar [4.0.2] Cannot satisfy dependency: >> From: WSO2 Carbon - Event Server Feature 4.0.5 >> (org.wso2.carbon.event.server.feature.group 4.0.5) To: >> org.wso2.carbon.event.server.feature.jar [4.0.5] Cannot satisfy dependency: >> From: WSO2 Carbon - Mediation Initializer Server Feature 4.0.2 >> (org.wso2.carbon.mediation.initializer.server.feature.group 4.0.2) To: >> org.wso2.carbon.event.server.feature.group [4.0.2] Cannot satisfy >> dependency: From: WSO2 Carbon - BAM Mediator Aggregate Feature 4.0.5 >> (org.wso2.carbon.mediator.bam.feature.group 4.0.5) To: >> org.wso2.carbon.mediator.bam.server.feature.group [4.0.5] Cannot satisfy >> dependency: From: WSO2 Carbon - BAM Mediator Feature 4.0.5 >> (org.wso2.carbon.mediator.bam.server.feature.group 4.0.5) To: >> org.wso2.carbon.mediation.initializer.server.feature.group [4.0.0,4.1.0) >> >> In summary; >> >> The root cause here again is features including external features as a >> nested part of it instead of properly* importing external features*. >> In org.wso2.carbon.mediator.bam.server.feature 4.0.5 it has a dependency >> to org.wso2.carbon.mediation.initializer.server.feature:4.0.2. >> >> In org.wso2.carbon.mediation.initializer.server.feature:4.0.2, the >> event.server.feature:4.0.2 is included instead of being imported. Hence the >> above conflict in installation as AS 5.0.2 has event.server.feature:4.0.5 >> already installed and doesn't allow it's lower versioned (4.0.2) get >> installed as part of >> org.wso2.carbon.mediation.initializer.server.feature:4.0.2 >> >> If we are to fix this need to update mediation.initializer.server.feature >> to properly import the server.feature. How to proceed with this? >> >> Thanks, >> Dileepa >> >> -- >> Dileepa Jayakody, >> Software Engineer, WSO2 Inc. >> Lean . Enterprise . Middleware >> >> Mobile : +94777-857616 >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > -- Dileepa Jayakody, Software Engineer, WSO2 Inc. Lean . Enterprise . Middleware Mobile : +94777-857616
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
