Thanks Greg. I have a multi-module Maven build that I deploy to Maven central. I do this via oss.sonatype.org as a staging repository. Perhaps Apache has its own workflow. But if you need some help with that do ask. Its a hassle to set it up, but once you are there putting out a new build into the Maven repo becomes very easy.
Rupert On 16 December 2014 at 17:12, Greg Trasuk <[email protected]> wrote: > > > Hi Rupert: > > Oops! It looks like we did not include ‘tools.jar’ in the jar files that > are deployed to Central (as you probably know, the > build is still based on Ant, but then we do a semi-manual deployment to > Central for the convenience of Maven users). ‘tools.jar’ continues to be in > the actual build, it just isn’t on Central. > > Given a day or two I can add in ‘tools.jar’ to the 2.2.2 release - I’ll > have to do a completely manual deployment, which I’ll have to figure out > how to do. > > Here’s a couple of options for you to get going now: > > 1 - You could either build from the source distribution or grab the binary > distribution and then manually install tools.jar to your local maven cache > using the instructions at > http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html. If > you build from source, please keep in mind you need to build using a ‘Java > 7' JDK. > > 2 - I’m in the process of stripping-out and mavenizing the tools and start > modules. As it stands at this instant, the ServiceStarter is working, but > I haven’t yet tested ClassServer, although I’m pretty sure it should work. > You could grab the source code from > http://svn.apache.org/repos/asf/river/river-rt-tools/trunk, and then do a > ‘mvn install’ to install the tools.jar snapshot to your local repository > (you can lookup the GAV coordinates in the module’s pom file). > > I’d suggest option 2, since that’s the way we’re moving to in the future. > I’m hoping to call for a release of the river-rt-tools modules in a week or > two, at which point we likely will remove them from the 2.2 branch and > release 2.2.3 without them (although they might just be deprecated - that’s > a different discussion). Also at that time, the tools jar will be deployed > to Central. > > Cheers, > > Greg Trasuk. > > > > On Dec 16, 2014, at 10:36 AM, Rupert Smith <[email protected]> > wrote: > > > Hi, > > > > I am upgrading some code from River 2.1.2 to 2.2.2, primarily because the > > 2.2.2 artifacts are available on Maven central repo, making it easier to > > get up and running with. > > > > I have been using com.sun.jini.tool.ClassServer, to serve up .jars over > > HTTP, which is pretty easy to use like this: > > > > classServer = new ClassServer(port, libDir, false, true, true); > > classServer.start(); > > > > Has this been removed from 2.2.x? I can't seem to find it. Is there > > something equivalent to replace it if so? > > > > Rupert > >
