Thanks for the quick reply. Then the best way to get the current version is directly using Subversion? It looks like you've baselined version 1.0.0 already.
My personal preference on packaging would include all providers in a single package. Seems like this would help to eliminate incompatibilities between the NMS base and the providers. Regarding the assemblies, I like the way that Spring.NET is distributed. It contains assemblies by .NET version with release and debug assemblies. In browsing the packages I noticed the WCF provider. I'm very interested in this, can you provide a brief description? Thanks again. - Will semog wrote: > > Hi Will, > > It wasn't intentionally removed, it just hasn't been filled in yet. I > have some semi-official binaries built, but have not created a single > package of them yet. I am working on the scripts that will take the > binaries and create a single download file. I haven't decided the > best way of packaging them. It may be that each provider will get its > own download package, and users will be able to pick and choose which > packages to download. I think this may be better than a single > package that includes all provider implementations. > > Thoughts on the best way to package up the assemblies? > > -Jim > > -- View this message in context: http://www.nabble.com/NMS-Download--tp20508850p20510135.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
