Re: Importing from a Jar file WITHOUT unzipping it

Andreas Leitgeb wrote:
Lew <noone@xxxxxxxxxxxxx> wrote:
Mark Space wrote:
Just pointing to the directory won't work, that's for loose classes.
It will if you wildcard the directory:
-classpath /some/path/lib/*

Are you talking about some new feature of 1.6.0_10 here?

<http://java.sun.com/javase/6/docs/technotes/tools/solaris/classpath.html>
Class path entries can contain the basename wildcard character *, which is considered equivalent to specifying a list of all the files in the directory with the extension .jar or .JAR.

It came out before update 10.

If you're using obsolete or obsolescent versions of Java, YMMV.

--
Lew
.

Relevant Pages

  • Re: Importing from a Jar file WITHOUT unzipping it
    ... in the directory with the extension .jar or .JAR. ... If you're using obsolete or obsolescent versions of Java, ... this feature has been in place for two years now. ...
    (comp.lang.java.programmer)
  • Re: new mcse 2000
    ... >> JaR ... >> Cognocente Candidate ... > IF you are an obsolete Italian. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Importing from a Jar file WITHOUT unzipping it
    ... which is considered equivalent to specifying a list of all the files in the directory with the extension .jar or .JAR. ... If you're using obsolete or obsolescent versions of Java, ...
    (comp.lang.java.programmer)
  • Re: OracleDriver load fails from a Web Service On tomcat
    ... Do not change the extension to jar. ... in $TOMCAT_HOME/common/lib and then bounce Tomcat. ... Java 1.3 is already obsolete and Java 1.4 is obsolescent. ...
    (comp.lang.java.programmer)
  • Re: Unable to execute program using the jar option.
    ... by specifying the class directly it runs just ... looks only in the JAR manifest for its class paths. ... You can only specify one JAR file, which must contain all the application-specific code. ... all user classes come from the specified archive. ...
    (comp.lang.java.programmer)
Loading