It appears that someone has uploaded a number of the River jar & zip files as artifacts to the mvnRepository site (http://mvnrepository.com/search.html?query=jsk-platform). That is,
jsk-platform.jar, jsk-lib.jar, jsk-resources.jar jini-core.jar, jini-ext.jar, jini-starterkit.zip, jini-start-examples.zip Thanks to that person/people, by the way. Although poms corresponding to each of the jar files that are produced by a river build were created and checked in to the river repository (https://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/poms), it appears that many of the other jar files from the build were not uploaded. In particular, start.jar, tools.jar reggie.jar, reggie-dl.jar outrigger.jar, outrigger-logstore.jar, outrigger-snaplogstore.jar mahalo.jar, mahalo-dl.jar etc. Was there a reason these other jar artifacts were excluded? (I'm not a maven user so I admit that I may be unfamiliar with the conventions of maven and that repository). If not, is there a mechanism or protocol for getting them included? [As a side note, for what it's worth, if folks are still using jini-core.jar and jini-ext.jar, they should consider no longer using those jars; and use jsk-platform.jar, jsk-resources.jar, and jsk-lib.jar instead.] Thanks for any help and/or insight regarding this issue, Brian
