[jsword-devel] Updates

[Joe Walker]

I meant to add that SwordBibleDriver gets it's Bible data from the
"Bibles.Sword.Base\ Directory" resource in Tools.properties

Joe.

On Mon, 2002-07-29 at 02:43, Joe Walker wrote:
> 
> This is how SerBibleDriver (and all BibleDrivers except
> SwordBibleDriver) find their resources:
> 
> The constructor calls something like:
>    NetUtil.lengthenURL(Project.resource().getBiblesRoot(), "ser");
> 
> NetUtil.lengthenURL simply takes a base url (in this case the Bibles
> root dir) and adds a 'subdirectory'.
> 
> Project.resource().getBiblesRoot() looks through the classpath and at
> each entry and looks for a directory called "versions" at that level. It
> should give you plenty of debug telling you where it is looking.
> 
> When I run from the command line (./tools.sh) I get:
> --
> looking for Bibles local classpath entry file:./jsword.jar: [Found at
> file:./versions]
> --
> 
> i.e. it found a versions directory next to the jsword jar file.
> However if I run from eclipse without adding any unpacked ser file I get
> the following:
> --
> looking for Bibles within /home/.../crimson.jar: [Not Found]
> looking for Bibles within /home/.../jaxp.jar: [Not Found]
> looking for Bibles within /home/.../jdom.jar: [Not Found]
> looking for Bibles within /home/.../xalan.jar: [Not Found]
> looking for Bibles within /home/.../jlfgr-1_0.jar: [Not Found]
> looking for Bibles within /home/.../servlet.jar: [Not Found]
> looking for Bibles within /home/.../junit.jar: [Not Found]
> looking for Bibles within /home/.../jsword/target/eclipse/classes: [Not
> Found]
> --
> 
> Leaving me with a JSword window with no Bible data.
> However all I need to do is to add target/ant/deploy/jsword/resources to
> the classpath and it finds the versions dir alongside the resources dir:
> --
> looking for Bibles local classpath entry
> file:/home/.../jsword/target/eclipse/classes/: [Not Found]
> looking for Bibles within /home/.../crimson.jar: [Not Found]
> looking for Bibles within /home/.../jaxp.jar: [Not Found]
> looking for Bibles within /home/.../jdom.jar: [Not Found]
> looking for Bibles within
> /home/.../jsword/target/ant/deploy/jsword/resource: [Found at
> file:/home/joe/devt/jsword/target/ant/deploy/jsword/versions]
> --
> 
> So to work out what is going wrong I need to see the few lines of debug
> like the above.
> 
> Joe.
> 
> On Sun, 2002-07-28 at 22:55, Mark Goodwin wrote:
> > > The #1 thing to check would be the following:
> > > $ ant deploy
> > > [blah blah]
> > > $ ls target/ant/deploy/jsword/versions
> > > ser
> > > 
> > > If you don't have a ser directory in the versions dir (or even no
> > > versions dir) then you don't have any Bible data installed, and we need
> > > to work out how that could be.
> > 
> > OK.  Here are the steps I took, and what hapened.
> > 
> > I started off with a clean machine (no previous jsword / projectb
> > installation, no ~/.jsword dir). Debian GNU/Linux 2.2 on an i386, if
> > that matters....
> > 
> > I did a cvs co, and copied the zip file containing the AV ser data from
> > the projectb download section at sourceforge to
> > notes/versions/projectb-ser-av.zip
> > 
> > Once I'd done that, I got ant 1.5 and attempted a build.
> > 
> > It all built beautifully, but when I attempt to run from
> > target/ant/deploy/jsword, it fails to find a version - lo and behold no
> > versions dir.
> > 
> > MarkG
> > 
>