+1 for the option 1, since no one else is using these components other than MB. But we should have separate modules for each (MB-Core, AMQP transport and MQTT transport) inside MB repo.
On Mon, Jun 20, 2016 at 3:40 PM, Asitha Nanayakkara <[email protected]> wrote: > Hi all, > > With the recent effort to decouple MB core from Qpid code we have moved > all the core functionalities of the broker, which are not relevant to > transports to product-mb repo [1] And kept all the Qpid related code in > andes repo [2]. Now the MB core has zero dependency to its transports. > > Dependency structure of components is as follows, > > > > *Issue:* > With the current changes we can't build the Andes repo first since we need > to build the MB core before that. When it comes to the product-mb repo, > AMQP component requires Andes repo to be built before AMQP component. Hence > a cyclic dependency for the build process. > > *Solutions:* > To overcome this probable solutions we came up with are, > > 1. Move Qpid code to the AMQP component to avoid the cyclic dependency > for build process. > 2. Have separate repositories for Qpid code (andes repo), AMQP, MQTT > and MB core so that we can build MB core first and then the transports > > What would be the best approach? > > > [1] https://github.com/wso2/product-mb > [2] https://github.com/wso2/andes > > Regards, > Asitha > -- > *Asitha Nanayakkara* > Senior Software Engineer > WSO2, Inc. http://wso2.com/ > Mob: +94 77 853 0682 > > -- Asanka Abeyweera Software Engineer WSO2 Inc. Phone: +94 712228648 Blog: a5anka.github.io
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
