Hi Rupert: It may take some time to get replicated into Central, but I’ve published tools.jar under the following gav coords:
<groupId>org.apache.river</groupId> <artifactId>tools</artifactId> <version>2.2.2</version> Cheers, Greg Trasuk. On Dec 17, 2014, at 4:31 AM, Greg Trasuk <[email protected]> wrote: > > There will be a new tools.jar with much the same content, including > ClassServer. It will just be a different gav coordinate and a different > package name. > > The basic problem is that the ‘tools.jar’ that we currently have contains a > circular dependency. ‘tools.jar’ currently contains the ‘ClassDepend’ tool, > which is used in building the River jar files, but ‘tools.jar’ also contains > classes that reference classes that are in ‘jsk-lib.jar’ and > ‘jsk-platform.jar’. So, we’re splitting out the build tools from the runtime > tools and pulling them both out of the main River build. Also making them a > Maven build. > > You can browse the runtime tools project currently in svn at: > http://svn.apache.org/viewvc/river/river-rt-tools/trunk/ > If you’re familiar with Maven I’m sure you’ll get the gist of it. > > Cheers, > > Greg. > > On Dec 17, 2014, at 4:16 AM, Rupert Smith <[email protected]> > wrote: > >> On 16 December 2014 at 17:12, Greg Trasuk <[email protected]> wrote: >>> >>> 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. >> >> >> If the tools.jar is being deprecated, is something else replacing it? Is >> there some other way in which the same thing can be done on 2.2.3? >> >> Rupert >
