Hi IS/Jaggery team, We have tried to use latest carbon-identity, but this lead to an issue in AS. The product startup failed. Upon further inspection, it seems like the rampart bundle state is INSTALLED. The error is at [1]. It seems the error is because of having two wss4j bundles.
The wss4j 1.5.11.wso2v11 is coming from security mgt feature while the org.jaggeryjs.modules.ws ships wss4j 1.5.11.wso2v9. @Manu, Jaggery team, can we stop packing wss4j and rampart bundles from jaggery-extensions? This is coming from [2]. @IS team, Is it possible to broaden the Import-Package version range? The current range ,[1.5.11.wso2v11,2.0.0), forces everyone to be on 1.5.11.wso2v11 or later. [1] BundleException: The bundle "rampart-core_1.6.1.wso2v16 [357]" could not be resolved. Reason: Package uses conflict: Import-Package: org.apache.ws.security; version="*[1.5.11.wso2v11,2.0.0)*", Package uses conflict: Import-Package: org.apache.ws.security.components.crypto; version="[1.5.11.wso2v11,2.0.0)", Package uses conflict: Import-Package: org.apache.ws.security.handler; version="[1.5.11.wso2v11,2.0.0)", Package uses conflict: Import-Package: org.apache.ws.security.message; version="[1.5.11.wso2v11,2.0.0)", Package uses conflict: Import-Package: org.apache.ws.security.message.token; version="[1.5.11.wso2v11,2.0.0)", Package uses conflict: Import-Package: org.apache.ws.security.saml; version="[1.5.11.wso2v11,2.0.0)", Package uses conflict: Import-Package: org.apache.ws.security.util; version="[1.5.11.wso2v11,2.0.0)" [2] https://github.com/wso2/jaggery-extensions/blob/master/ws/feature/pom.xml#L112 -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
