In this post let us see the proper order of building the WSO2 Identity Server components without any dependency failures.
Sometimes we might need to do customisations or fix bugs in the "carbon-identity-framework" components (Or any other components).
For example, recently i encountered a scenario where i was suppose to back-port a fix from the newer "carbon-identity-framework" authenticationendpoint.war version to an older authenticationendpoint.war.
After back-porting the fix i was unable to build the patched authenticationendpoint.war file due to some missing dependencies in the .m2 repository. By following a proper order to build the components we can overcome these issues.
Order to build WSO2 components
1. WSO2 Orbit Repository (https://github.com/wso2-support/orbit) Only has the master branch. Provides some dependencies to build the Carbon Kernel.
2. WSO2 Carbon4 Kernel (https://github.com/wso2-support/carbon4-kernel) Relevant branch depending on the Product and the version should be built.
3. WSO2 Carbon Consent Management (https://github.com/wso2-support/carbon-consent-management) Relevant version included in the Product can be found in the <IS_HOME>/repository/components/plugins/ directory.
For Identity Server 5.8.0 it is "support-2.0.27" version.
4. WSO2 Identity Server Framework (https://github.com/wso2-support/carbon-identity-framework). Relevant branch depending on the Identity Server version should be built.
5. WSO2 Identity Server Inbound and Outbound Authenticators.
It is not always necessary to start building from the order, but if in case there are some missing dependencies then the above is the order to follow. Thank you for reading!!!
Comments