I've read thoroughly the manual and examples but still can't find the reason
for this behavior. First, some pointers to state my case.
- Environment: Windows XP SP3, Ant 1.8.1, jdk1.6.0_02
- My project builds and run fine from the cmdline, provided that the CLASSPATH
env. variable is set. I can
Woah, thanks Scot! That's a FAST reply, and a good one I think.
If nothing else, it helped me to rule out some possible causes of error.
To answer your question, I intend to collect my buildfiles in a separate
folder, sibling to the projects root, and that's the current dir when I fire
"ant".
Good news:
yields:
D:\Workspaces\Java\projects\modules
instead of the expected:
D:\Workspaces\Java\projects\modules\src
Surely something's going wrong when processing the includes="" property (or the
nested elements, it's the same).
> I bet basename will yield src?
Exactly. I typed in the following lines, as suggested:
dir = [${basedir.dir}]
base = [${basedir.basename}]
Side notes:
- versose output contains the line
Project base dir set to: D:\Workspaces\Java
- source code for project's main class begins
> You might try to compute the dir and hand that value to
> javac...
>
> For example:
>
> property="basedir.basename"/>
>
>
> .../>
>
>
> Not sure that will fix it...but it may :)
It didn't in fact.
Thanks anyway for all the help.
-
Update:
Finally I managed to compile and jar the content of the src dir.
This is the updated build.properties file:
src.dir=${basedir}/projects/modules/src
build.dir=${basedir}/projects/WEB-INF/build
dist.dir=${basedir}/projects/WEB-INF/dist
project.name=gdv
main-class=apps.gdv.GDVLauncher
jar-cl
SOLVED:
Still I can't say why all / statements fail in my
configuration, but at last I found a workaround. I'll post it in case someone
had similar issues.
build.properties
src.dir=${basedir}/projects/modules/src
# I overlooked subpackage sr2 previously, but that's not essential
