eee96b1bb0
2007-01-10 Matthias Klose <doko@debian.org> Readd missing chunks from r116332: * m4/acinclude.m4 (CLASSPATH_TOOLEXECLIBDIR): New macro. * resource/Makefile.am (loggingdir): Define to toolexeclibdir. (securitydir): Likewise. * configure.ac: Call CLASSPATH_TOOLEXECLIBDIR. Set default nativeexeclibdir using toolexeclibdir. Readd missing chunks from r115839: * native/jni/gtk-peer/Makefile.am (libgtkpeer_la_LDFLAGS): Add -avoid-version. * native/jawt/Makefile.am (libjawt_la_LDFLAGS): Add -avoid-version. * configure, Makefile.in, doc/Makefile.in, doc/api/Makefile.in, examples/Makefile.in, external/Makefile.in, external/jsr166/Makefile.in, external/relaxngDatatype/Makefile.in, external/sax/Makefile.in, external/w3c_dom/Makefile.in, include/Makefile.in, lib/Makefile.in, native/Makefile.in, native/fdlibm/Makefile.in, native/jawt/Makefile.in, native/jni/Makefile.in, native/jni/classpath/Makefile.in, native/jni/gconf-peer/Makefile.in, native/jni/gtk-peer/Makefile.in native/jni/java-io/Makefile.in, native/jni/java-lang/Makefile.in, native/jni/java-net/Makefile.in, native/jni/java-nio/Makefile.in, native/jni/java-util/Makefile.in, native/jni/midi-alsa/Makefile.in, native/jni/midi-dssi/Makefile.in, native/jni/native-lib/Makefile.in, native/jni/qt-peer/Makefile.in, native/jni/xmlj/Makefile.in, native/plugin/Makefile.in, resource/Makefile.in, scripts/Makefile.in, tools/Makefile.in: Regenerate From-SVN: r120654 |
||
---|---|---|
.. | ||
asm/org/objectweb/asm | ||
classes/gnu/classpath/tools | ||
external | ||
gnu/classpath/tools | ||
.cvsignore | ||
appletviewer.in | ||
gappletviewer.in | ||
gjar.in | ||
gjarsigner.in | ||
gjavah.in | ||
gkeytool.in | ||
gnative2ascii.in | ||
gorbd.in | ||
grmic.in | ||
grmid.in | ||
grmiregistry.in | ||
gserialver.in | ||
gtnameserv.in | ||
jarsigner.in | ||
keytool.in | ||
Makefile.am | ||
Makefile.in | ||
README | ||
toolwrapper.c |
The GNU Classpath tools are stored in the tools.zip. They can be invoked by putting this archive into classpath and specifying the tool main class as the class to run (parameters usually follow). The current release contains the following tools: == GIOP tools == GIOP tools are used for creating the applications that use GIOP communication protocol. It provides necessary support for org.omg.* and javax.rmi.* packages. All GIOP tools support the --help option, for instance: java -cp tools.zip gnu.classpath.tools.giop.IorParser --help The list of the currently available GIOP tools (name matches the main class in gnu.classpath.tools.giop package): * GRMIC - RMI-IIOP stub and tie generator. * NameService - GIOP transient naming service (this tool is called tnameserv in Sun's package). * NameServicePersistent - GIOP persistent naming service (this tool is called orbd in Sun's package). * IorParser - Parses the stringified form of the interoperable object references (IOR's). == RMI tools == RMI tools provide support for java.rmi package. All tools support the --help key by printing more information, for instance: java -cp tools.zip gnu.classpath.tools.rmi.RMIC --help The list of the currently available RMI tools (name matches the main tool class in gnu.classpath.tools.rmi package): * RMIC - RMI stub and tie source code generator (complements the ASM based bytecode generator in the separate cp-tools project). This tool is only needed for research and backward-compatibile applications, as Classpath supports the 1.5 feature to replace such stubs by proxy classes. * REGISTRY - The persistent RMI naming service. * RMID - The persistent RMI activation daemon, supports the java.rmi.activation package. == Security tools == Security tools (currently) are used for signing and verifying JAR files as well as (planned) generating and managing cryptographic tokens and credentials. The list of individual tools, the name of their main class that should be invoked by the Java launcher, and a summary of what they provide follows: * jarsigner gnu.classpath.tools.jarsigner.Main A drop-in replacement for the "jarsigner" tool.