search

lukeme / gobible

Automatically exported from code.google.com/p/gobible
1 stars 0 forks source link

Relative paths for defaults and command line options #157

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Please ensure that when features are added to either the trunk or a branch of 
GoBibleCreator, that paths to external files are allowed to be relative, and 
not converted to absolute paths, even when defaults are assumed.

Failing to adhere to this advice can cause problems when other users do things 
differently to your own way of working.

See 
http://crosswire.org/wiki/Projects:Go_Bible/Go_Bible_Creator#Enhanced_techniques

Original issue reported on code.google.com by DFH...@gmail.com on 5 Jul 2011 at 7:16

GoogleCodeExporter commented 8 years ago 
It should remain feasible to use GoBibleCreator from anywhere, without having 
to change the current directory to where GoBibleCreator.jar is stored.

Thus if one has an environment variable called GBC_PATH set to the path where 
it's located, the following command line syntax should work anywhere on the 
computer.

java -Xmx128m -jar %GBC_PATH%\GoBibleCreator.jar collections.txt

or better still, using a CMD file with a passed parameter...

java -Xmx128m -jar %GBC_PATH%\GoBibleCreator.jar %1 1>.\java.log 2>.\error.log

Original comment by DFH...@gmail.com on 6 Jul 2011 at 6:22

GoogleCodeExporter commented 8 years ago 
I think this issue may be closed.

I'm using relative paths, as well as an environment variable as described.

I've not had any recent problems with my Windows CMD file method.

Original comment by DFH...@gmail.com on 31 Dec 2012 at 2:09