+1, we could break them down to maven modules under the transport parent module.
Thanks, Ruwan On Sat, Apr 4, 2009 at 5:36 PM, Andreas Veithen <[email protected]>wrote: > > Eric, I am not sure whether the amqp transport is functional or not, so I > > propose to remove the qpid plus all its dependencies from the build. > > Asankha, shall we move this (amqp transport) piece of code to the > experiment > > module, and retain it from being going to the final release or is it > > working? > > I think the amqp transport is basically dead. The reason is that it > initially started as a fork of the JMS transport (see also > SYNAPSE-303) and that in the meantime some serious issues have been > fixed in the JMS transport. These fixes have not been propagated to > the amqp transport. > > Instead of moving the amqp transport to experimental, why not split > the synapse-transport module and have a separate module for each > transport? This would make dependency management much easier because > it would be clear which dependency is used by which transport. Also > when using Maven to create a custom Synapse package [1], one could > simply select the required transports as dependencies and let Maven > handle the transitive dependencies. > > [1] > http://people.apache.org/~veithen/synapse/deployment.html#Using_Maven_to_build_a_custom_distribution<http://people.apache.org/%7Eveithen/synapse/deployment.html#Using_Maven_to_build_a_custom_distribution> > > Andreas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Ruwan Linton Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
