ant script annoyances
Herve Quiroz
herve.quiroz at esil.univ-mrs.fr
Thu Sep 11 09:01:20 PDT 2003
I agree with this. IMHO 'classpath-config' would be a good name for such
a tool. With the following options (or similar with different names):
--all -> CLASSPATH contains all JARs and subdirs from $JAVASHAREDIR.
--add -> Add selected paths and JARs in the current CLASSPATH variable
instead of overriding it.
--with-lib=<library_name> -> include the specified JAR in the
CLASSPATH. For example, '--with-lib=junit' would add the first JAR
file whose name starts with 'junit' in the JAVASHAREDIR directory.
The first two options are mandatory. The third could just be implemented
later. I only listed it here to demonstrate the usefulness of such a
tool for efficient java application coding/running.
Herve
On Thu, 11 Sep 2003, Ernst de Haan wrote:
> > The algorithm/script fragment that adds FreeBSD-specific jars to the
> > classpath is interesting *also* outside of Ant. Why not extract that
> > part and make it a shell script that could even be sourced within Ant if
> > the specific env variable is set?
>
> You are right. We should indeed provide a separate script for this. Question
> is how we distribute this script. But then it shouldn't be treated as part
> of Ant either.
>
> What if we make this a separate port, make Ant dependent on it, and *also*
> change the ant shell script to recognize an environment variable that will
> make it call that script?
>
> Ernst
More information about the freebsd-java
mailing list