Dear Paul and al, Thanks for your support. I have manually modified my build.properties so that it now matches with my local environement. Here is what I have now:
-----------------------------------------------------------------------
#user editable build configuration parameters
#Mon Jul 27 17:28:16 CEST 2009
cedet.dir=d\:/Programme/GNU/emacs-extension/cedet
elib.dir=d\:/Programme/GNU/emacs-extension/elib
build.bin.emacs=d\:/Programme/GNU/Emacs/bin/emacs.exe
config.time=2009/08/18 03\:32
prefix.dir=d\:/Programme/GNU/emacs-extension/jde
-----------------------------------------------------------------------
Nevertheless, I am still getting the same trouble. I attached the log of
build to this email.
It is as if before makeing the `exec' ant was testing whether the
directory d:/Programme/GNU/emacs-extension/jde-src/build/lisp exists,
and does not carry out this test properly.
Note that I made also a test with modifying the build.xml so that the
exec line is replaced by:
<exec dir="d:/Programme/GNU/emacs-extension/jde-src/build/lisp"
executable="${build.bin.emacs}" failonerror="true">
and I am getting exactly the same output (I did not backslash-escape the
`:' because this is an XML file, not a properties file).
Note also that this is the only exec statement in all the build.xml
file.
my ant version is
Apache Ant version 1.7.1 compiled on June 27 2008
Maybe it is possible to go around this issue by not specifying the
current directory at ant level, but by doing this in emacs-lisp like
this (which I did not try):
<exec dir="${build.lisp.dir}" executable="${build.bin.emacs}"
failonerror="true">
<arg value="--eval"/>
<arg value="(setq default-directory "${build.lisp.dir}")"/>
<arg value="--script"/>
<arg value="${build.lisp.dst.file}"/>
</exec>
Regards,
Vincent.
> From: [email protected]
> Date: Sun, 2 Aug 2009 17:59:26 -0500
> To: [email protected]
> CC: [email protected]; [email protected]; [email protected]
> Subject: Re: [jdee-users] jdb filter cannot interpret line numbers >= 1000
>
> The build has been tested on windows, so my guess it's an environment
> issue. I think the problem might be the back slashes. I'm not really
> sure from what I see here, but you'll need front slashes for
> everything (including environment variables).
>
> Here's my build.properties:
>
[SNIP]
build.log.gz
Description: Log file of my build
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ jdee-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdee-users
