> > > With that in mind, one strategy regarding river and maven to > consider might be that, rather than maven-izing the whole build > process as the first step (which may be a huge undertaking), > one might consider first placing the artifacts the current build > process produces -- minus the unnecessary artifacts described > above -- into a public maven repository; which is something that > has been discussed in the past by Jeff Ramsdale and other > maven experts on this list. This would then make it quite clear > what jar files are necessary to use river. Additionally, although > doing this as a first step is aimed at the users of river as opposed > to river developers/contributors, it still may be a useful thing to > do with respect to ease-of-use/deployment; and it may actually > provide a bigger bang for the buck than one might expect. > > Anyway, it's just a thought. >
Thank you. That is exactly what I meant above as well. As a first step, try to get the artifacts into a public repository.
