copyFiles ant error

6 views
Skip to first unread message

Shane Steinert-Threlkeld

unread,
Nov 16, 2008, 5:16:52 PM11/16/08
to jgrousedoc
When executing ant in my project directory, I get the following error:

copyFiles:

BUILD FAILED
/cis/home/shanest/public_html/js/mathnetics/build.xml:38: /cis/home/
shanest/public_html/js/mathnetics/skins not found.


Here is my jgrousedoc.properties file:

#set jGrouseHome - location of jGrouseDoc distribution
jGrouseHome.default=../../../jgrousedoc
#set the location of your source files
inputDir=src
#inputDir=../jgrouse-js/src
#Set mask for input files
fileMask=**/*.js
#fileMask=**/test*.js
#set output directory
outputDir=docs
#select skin - options are classic, modern and noframes
#skin=classic
#skin=modern
skin=noframes

#select theme
theme=simple
#theme=simple

#indicate if the process should stop on first error
stopOnErrors=false

outputFormat=bin
#outputFormat=xml

privatePrefix=_


#set encoding of project file
encoding=UTF-8
#set encoding of source files or leave as "DEFAULT"
srcEncoding=DEFAULT
#set flag whether warnings about implicit use of GLOBAL namespace
should be suppressed
suppressGlobalWarnings=false
#indicate if "browse by name" should be using full names or local
names
useFullNames=true



#OPTIONAL - set short name of your project, see also @project tag
projectName=Mathnetics
#OPTIONAL - set version of your product, see also @project tag
appVersion=1.0.0



#OPTIONAL - set the description of your project - it would appear on
startup page, see also @project tag
projectDesc=Mathmetical objects and 3-D rendering for Javascript (and
SVG)


#use aux_css parameter to specify the css file that should be used
#along with jgdoc.css (or whatever was overridden with "css"
parameter). Note - the name
#should be relative to the output directory. It is your responsibility
to copy that file over.
aux_css=not_specified
#name of jGrouseDoc output file
#projectFile=jgrouse.xml
projectFile=jgrouse.jgd
#default view for Modern theme
jgdoc.defaultView=navtree.html


jgdocTask=./bin

denis.r...@gmail.com

unread,
Nov 16, 2008, 5:24:41 PM11/16/08
to jgrousedoc
Shane,

Which build are you using - the one you built yourself from source
files or the downloaded binaries?

What is the absolute path for the directory containing jGrouseDoc
distribution?

Regards,
Denis

On Nov 16, 5:16 pm, Shane Steinert-Threlkeld <ssshan...@gmail.com>
wrote:

Shane Steinert-Threlkeld

unread,
Nov 16, 2008, 5:35:13 PM11/16/08
to jgrousedoc
I built from source into the absolute directory /cis/home/shanest/
jgrousedoc

denis.r...@gmail.com

unread,
Nov 16, 2008, 5:50:09 PM11/16/08
to jgrousedoc
Was the build from source successful? If I am not mistaken, you have
posted a bug into jGrouseDoc issues.

Are you running ANT from directory containing build.xml? it seems that
jGrouseDocHome directory was specified as a relative to your current
directory and ANT picks the wrong one. Either try to run ANT from the
same directory where you have build.xml for your project, or specify
absolute location for jGrouseDocHome.

Regards,
Denis

On Nov 16, 5:35 pm, Shane Steinert-Threlkeld <ssshan...@gmail.com>

denis.r...@gmail.com

unread,
Nov 16, 2008, 5:52:46 PM11/16/08
to jgrousedoc
Also, pls check which build.xml file you are using - the one that
builds the distribution from sources or the one that should be used to
process javascript files

On Nov 16, 5:35 pm, Shane Steinert-Threlkeld <ssshan...@gmail.com>

Shane Steinert-Threlkeld

unread,
Nov 16, 2008, 5:56:43 PM11/16/08
to jgrou...@googlegroups.com
Same error with absolute path.

How do I check which build.xml file I am using? I copied the one from
the jGrouse sources to the current working directory...
Reading it, it does seem that it is not the one to process JS files...

denis.r...@gmail.com

unread,
Nov 16, 2008, 6:01:34 PM11/16/08
to jgrousedoc
I think that's exactly the reason - you're using wrong build.xml file.

If you're building from source files, you need the one that is copied
out to the created jGrouseDoc distribution.
You can also find it in source archive under scripts directory - there
should be two files, build.xml and jgrousedoc.properties

Regards,
Denis

On Nov 16, 5:56 pm, Shane Steinert-Threlkeld <ssshan...@gmail.com>
wrote:

Shane Steinert-Threlkeld

unread,
Nov 16, 2008, 6:10:46 PM11/16/08
to jgrou...@googlegroups.com
You were right, but now I'm getting the same JGTask error as the
previous thread in this group... except that my path is I believe
entered correctly as "/cis/home/shanest/jgrousedoc"

denis.r...@gmail.com

unread,
Nov 16, 2008, 6:22:22 PM11/16/08
to jgrousedoc
Check if your build from the source was correctly done.
Under /cis/home/shanest/jgrousedoc you should see:
- themes (directory)
- skins (directory)
- sample (directory)
- 3rdparty (directory)
- velocity-dep-1.5.jar
- jgdoc.jar
- license.txt
- jgrousedoc.properties
- build.xml

can you please send the output of "ls -l" from that dir?

On Nov 16, 6:10 pm, Shane Steinert-Threlkeld <ssshan...@gmail.com>
wrote:
> You were right, but now I'm getting the same JGTask error as the
> previous thread in this group... except that my path is I believe
> entered correctly as "/cis/home/shanest/jgrousedoc"
>

Shane Steinert-Threlkeld

unread,
Nov 16, 2008, 6:31:40 PM11/16/08
to jgrou...@googlegroups.com

drwxr-xr-x 4 shanest shanest 31 Nov 16 16:24 3rdparty
-rw-r--r-- 1 shanest shanest 6834 Nov 16 16:25 build.xml
drwxr-xr-x 2 shanest shanest 116 Nov 16 16:24 docs
-rw-rw-r-- 1 shanest shanest 823303 Nov 16 18:08 jGrouseDoc-2.0.zip
-rw-r--r-- 1 shanest shanest 1684 Nov 16 16:25 jgrousedoc.properties
-rw-r--r-- 1 shanest shanest 207 Nov 16 16:25 license-header.properties
-rw-r--r-- 1 shanest shanest 1590 Nov 16 16:25 license.txt
drwxr-xr-x 3 shanest shanest 88 Nov 16 16:24 sample
drwxr-xr-x 2 shanest shanest 50 Nov 16 16:24 scripts
drwxr-xr-x 6 shanest shanest 61 Nov 16 16:24 skins
drwxr-xr-x 3 shanest shanest 20 Nov 16 16:24 src
drwxr-xr-x 4 shanest shanest 32 Nov 16 16:24 themes
-rw-r--r-- 1 shanest shanest 698567 Nov 16 16:25 velocity-dep-1.5.jar

denis.r...@gmail.com

unread,
Nov 16, 2008, 6:49:31 PM11/16/08
to jgrousedoc
The source build process created the distribution archive
jGrouseDoc-2.0.zip
Unpack it in a directory and use that directory as jGrouseDocHome

Regards,
Denis

On Nov 16, 6:31 pm, Shane Steinert-Threlkeld <ssshan...@gmail.com>
wrote:
> drwxr-xr-x  4 shanest shanest     31 Nov 16 16:24 3rdparty
> -rw-r--r--  1 shanest shanest   6834 Nov 16 16:25 build.xml
> drwxr-xr-x  2 shanest shanest    116 Nov 16 16:24 docs
> -rw-rw-r--  1 shanest shanest 823303 Nov 16 18:08 jGrouseDoc-2.0.zip
> -rw-r--r--  1 shanest shanest   1684 Nov 16 16:25 jgrousedoc.properties
> -rw-r--r--  1 shanest shanest    207 Nov 16 16:25 license-header.properties
> -rw-r--r--  1 shanest shanest   1590 Nov 16 16:25 license.txt
> drwxr-xr-x  3 shanest shanest     88 Nov 16 16:24 sample
> drwxr-xr-x  2 shanest shanest     50 Nov 16 16:24 scripts
> drwxr-xr-x  6 shanest shanest     61 Nov 16 16:24 skins
> drwxr-xr-x  3 shanest shanest     20 Nov 16 16:24 src
> drwxr-xr-x  4 shanest shanest     32 Nov 16 16:24 themes
> -rw-r--r--  1 shanest shanest 698567 Nov 16 16:25 velocity-dep-1.5.jar
>

Shane Steinert-Threlkeld

unread,
Nov 16, 2008, 9:36:22 PM11/16/08
to jgrou...@googlegroups.com
Configured as you described and now have the file hierarchy recommended,
but still getting the same JGTask error
denis.r...@gmail.com

denis.r...@gmail.com

unread,
Nov 16, 2008, 9:41:14 PM11/16/08
to jgrousedoc
OK, what is the setting of jGrouseDocHome property and what is the "ls
-l" content of that directory?

On Nov 16, 9:36 pm, Shane Steinert-Threlkeld <ssshan...@gmail.com>
wrote:
> Configured as you described and now have the file hierarchy recommended,
> but still getting the same JGTask error
> denis.riabtc...@gmail.com

Shane Steinert-Threlkeld

unread,
Nov 16, 2008, 9:49:57 PM11/16/08
to jgrou...@googlegroups.com
#set jGrouseHome - location of jGrouseDoc distribution
jGrouseHome.default=/cis/home/shanest/jgdoc/jGrouseDoc-2.0



drwxr-xr-x 4 shanest shanest 31 Nov 16 18:08 3rdparty
drwxrwxr-x 4 shanest shanest 255 Nov 16 21:35 api
-rw-r--r-- 1 shanest shanest 8336 Nov 16 18:08 build.xml
-rw-r--r-- 1 shanest shanest 81333 Nov 16 18:08 jgdoc.jar
-rw-r--r-- 1 shanest shanest 398 Nov 16 18:08 jgrousedoc.properties
-rw-r--r-- 1 shanest shanest 1590 Nov 16 18:08 license.txt
drwxr-xr-x 3 shanest shanest 88 Nov 16 18:08 sample
drwxr-xr-x 6 shanest shanest 61 Nov 16 18:08 skins
drwxr-xr-x 4 shanest shanest 32 Nov 16 18:08 themes
-rw-r--r-- 1 shanest shanest 698567 Nov 16 18:08 velocity-dep-1.5.jar

denis.r...@gmail.com

unread,
Nov 17, 2008, 7:21:23 AM11/17/08
to jgrousedoc
OK, i think I nailed it.
As I understand, you were using the file jgrousedoc.properties from
the root directory of the source distribution. Heh, that file is
tailored for testing of the java code.
The setting that prevents it working in your case is the last line
jgdocTask=./bin
Just comment it out.

The simplest thing is to modify the jgrousedoc.properties from the
generated distribution (in the source zip it appears in scripts
directory).

Regards,
Denis



On Nov 16, 9:49 pm, Shane Steinert-Threlkeld <ssshan...@gmail.com>
wrote:
> #set jGrouseHome - location of jGrouseDoc distribution
> jGrouseHome.default=/cis/home/shanest/jgdoc/jGrouseDoc-2.0
>
> drwxr-xr-x  4 shanest shanest     31 Nov 16 18:08 3rdparty
> drwxrwxr-x  4 shanest shanest    255 Nov 16 21:35 api
> -rw-r--r--  1 shanest shanest   8336 Nov 16 18:08 build.xml
> -rw-r--r--  1 shanest shanest  81333 Nov 16 18:08 jgdoc.jar
> -rw-r--r--  1 shanest shanest    398 Nov 16 18:08 jgrousedoc.properties
> -rw-r--r--  1 shanest shanest   1590 Nov 16 18:08 license.txt
> drwxr-xr-x  3 shanest shanest     88 Nov 16 18:08 sample
> drwxr-xr-x  6 shanest shanest     61 Nov 16 18:08 skins
> drwxr-xr-x  4 shanest shanest     32 Nov 16 18:08 themes
> -rw-r--r--  1 shanest shanest 698567 Nov 16 18:08 velocity-dep-1.5.jar
>

Shane Steinert-Threlkeld

unread,
Nov 17, 2008, 4:51:11 PM11/17/08
to jgrou...@googlegroups.com
Nail it you did! Thanks so much for your superb support.

I would recommend, however, that you expand the documentation on
building from source as it was not as simple as unpacking the archive
that I downloaded.
Reply all
Reply to author
Forward
0 new messages