> The point here is to first provide conventions for developers that use Maven > to be able to easily create and start services that use River.
That is a good goal, yes. >> The client should have an easy way to get at the API jars, >> yes, but the client will also need access to the DL jars at runtime. >> They shouldn't have to download the same jar files again and again. >> Maven has the advantage of having active development, a known and >> fairly straightforward repository structure, etc. so that's been >> proposed for part of the implementation. > > And I was all for that when we discussed it, and I dont think it needs to be > part of closing out release 2.2.0. You are right, it does not. The thread has gotten a bit messy, I apologize if I misunderstood. Patrick
