Hi all, I'm trying to build AS product + service on trunk. But I found out that in order to build this, I need to build synapse + mediation-initializer + mediators etc.. So it looks like we have to build almost the entire platform to build a particular product + service.
When I drill down the problem further, I found out that the features/stratos/common/org.wso2.carbon.stratos.common.server.feature depends on org.wso2.carbon:org.wso2.carbon.task:jar:3.2.0-SNAPSHOT and that is the only reason we have to build all ESB related stuff to build any stratos service. Do we really need tasks for each and every Straots service? If not can we separate it out from the core stratos components? I think we have to improve this somehow. Otherwise all product teams will end up building the entire platform which is a waste of time. Thanks, ~Isuru -- Isuru Suriarachchi Technical Lead & Product Manager, WSO2 Application Server WSO2 Inc. http://wso2.com email : [email protected] blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
