Thread: [tcljava-dev] How stable is Jacl 1.3.0 ?

The current jacl 1.3.0 tar file includes a README that begins:

-----

Before going any farther, it needs to be made clear that this release
of Jacl is not considered stable enough to be used in production
systems. 

-----

Any projections on when a release might occur that is considered stable
enough to be used in production systems?
-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

Well, after doing a configure, make, and make test (and seeing only 7
failures - not bad) I wanted to try out jacl 1.3.0 so I tried to run
the jaclsh script.  However, despite the fact that the make test works,
the jaclsh script only generates the error:
Exception in thread "main" java.lang.NoClassDefFoundError: tcl/lang/Shell

Now, I have my CLASSPATH exported and pointing to the directory where the
jacl.jar is located.  Is there something else that needs to happen to
get the script to work?
-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

On Tue, 24 Jun 2003 10:19:32 -0400 (EDT)
"Larry W. Virden" <lv...@ca...> wrote:

> the jaclsh script only generates the error:
> Exception in thread "main" java.lang.NoClassDefFoundError: tcl/lang/Shell
> 
> Now, I have my CLASSPATH exported and pointing to the directory where the
> jacl.jar is located.  Is there something else that needs to happen to
> get the script to work?

The jaclsh script should set all the CLASSPATH stuff for you. I would suggest that
you unset whatever CLASSPATH you currently have set and try it again. I can't
imagine why this would not work, it should. Are you running under Win32?
Perhaps the problem is with ; vs : characters in the CLASSPATH. Just an FYI,
a CLASSPATH should include the full path name of a .jar file, not just the
dir where a .jar file lives.

cheers
Mo

Mo DeJong <md...@un...> writes:
: On Tue, 24 Jun 2003 10:19:32 -0400 (EDT)
: "Larry W. Virden" <lv...@ca...> wrote:
: 
: > the jaclsh script only generates the error:
: > Exception in thread "main" java.lang.NoClassDefFoundError: tcl/lang/Shell
: > 
: > Now, I have my CLASSPATH exported and pointing to the directory where the
: > jacl.jar is located.  Is there something else that needs to happen to
: > get the script to work?
: 
: The jaclsh script should set all the CLASSPATH stuff for you. I would suggest that
: you unset whatever CLASSPATH you currently have set and try it again. I can't
: imagine why this would not work, it should. Are you running under Win32?
: Perhaps the problem is with ; vs : characters in the CLASSPATH. Just an FYI,
: a CLASSPATH should include the full path name of a .jar file, not just the
: dir where a .jar file lives.


$ unset CLASSPATH
$ $PWD/jaclsh
Exception in thread "main" java.lang.NoClassDefFoundError: tcl/lang/Shell
$ ls
Makefile          casrun.cas        jacl.jar          tcljava.jar
Test.class        config.log        jaclsh            tcljavaConfig.sh
Test.tcl          config.status     license.terms
btests            jacl              tcljava
$ CLASSPATH=$PWD/jacl.jar
$ export CLASSPATH
$ $PWD/jaclsh            
Exception in thread "main" java.lang.NoClassDefFoundError: tcl/lang/TclException
$ uname -a
SunOS lwv26awu 5.8 Generic_108528-16 sun4u sparc SUNW,Sun-Blade-100
$ echo $SHELL
/bin/ksh
$

-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

On Tue, 24 Jun 2003 09:59:49 -0400 (EDT)
"Larry W. Virden" <lv...@ca...> wrote:

> The current jacl 1.3.0 tar file includes a README that begins:
> 
> -----
> 
> Before going any farther, it needs to be made clear that this release
> of Jacl is not considered stable enough to be used in production
> systems. 
> 
> -----
> 
> Any projections on when a release might occur that is considered stable
> enough to be used in production systems?

It will be considered "ready for production use" when people try it in
production systems and it works without problems. It is a chicken and
the egg problem. If you ask me, the 1.3.0 release is in a much better state
than the 1.2.6, but there is a bunch of new code so it needs to be tested
in real systems.

Mo