Ok.. The code has been moved and it seems to build fine using the VS2005 project files. The build methods still need to get updated. But while we are re-orging this stuff..I think it might be a good time to bing the module naming conventions to match up.
Right Now: * NMS module uses the namespace Apache.NMS and produces a NMS.dll. * NMS.ActiveMQ module uses the namespace Apache.ActiveMQ and produces a NMS.ActiveMQ.dll. * NMS.MSMQ module uses the namespace Apache.MSMQ and produces a NMS.MSMQ.dll. * NMS.EMS module uses the namespace Apache.TibcoEMS and produces a NMS.EMS.dll. I propose that we make the module name, namespace, and dll names match. Those being: Apache.NMS, Apache.NMS.ActiveMQ, Apache.NMS.MSMQ, and Apache.NMS.EMS Any objections?? On 10/29/07, James Strachan <[EMAIL PROTECTED]> wrote: > Sounds great! :) > > > On 29/10/2007, Hiram Chirino <[EMAIL PROTECTED]> wrote: > > Yay.. > > > > The Tibco NMS Code Drop is now committed.. The associated IP clearance > > form is here: > > http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/activemq-nms-tibco.xml > > > > Many thanks go out to Jim Gomes and Tideworks Technology, Inc. That > > was an awesome contribution. > > > > Now that it's in, I'm planning on doing a little bit of house cleaning > > in regards to the svn repo organization of the modules. Right now we > > have the NMS API, the ActiveMQ, MSMQ, and Tibco modules all basically > > building from the same project. Since I think all those guys need to > > have independent release cycles, I'm going to split them up into > > individual svn projects. > > > > Also going to rename the NMS.Tibco module to NMS.4EMS since this > > module is specific to EMS.. If you guys have any issues with this > > please speak up. Going to start hacking this up soon. > > > > > > -- > > Regards, > > Hiram > > > > Blog: http://hiramchirino.com > > > > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source SOA > http://open.iona.com > -- Regards, Hiram Blog: http://hiramchirino.com
