dev@jsftemplating.java.net

problem with jsf templating builds

From: Michael Phoenix <michaelandrewphoenix_at_gmail.com>
Date: Mon, 22 Jan 2007 18:34:14 -0800

Ken,

I haven't any idea what could be wrong with ant. I am using 1.7.0 and have
set the ANT_HOME and JAVA_HOME exactly as described in the Ant installation
instructions. I also added the C:\ant\bin to my PATH variable.

Here's my environment variables
PATH C:\Sun\AppServer\bin;;;C:\Program Files\SSH Communications Security\SSH
Secure Shell;C:\Program Files\Java\jdk1.5.0_06\bin;C:\ant\bin;C:\Program
Files\cvsnt
CLASSPATH C:\Program
Files\Java\jre1.5.0_06\lib\ext\QTJava.zip;C:\Sun|AppServer\lib;.
ANT_HOME C:\ant
JAVA_HOME C:\Program Files\Java\jdk1.5.0_06

The line that is the problem appears to be executing a version of
ant.batthat was included in the jsft project.
*Execute failed: java.io.IOException : CreateProcess: lib\ant\bin\ant.bat -f
aptbuild.xml -lib lib/external/ant-apt.jar compile error=2*

I'm not sure how to begin debugging it, but I really don't see what it has
to do with my ant installation.


Karang,

In build.projects glassfish-home=C:/SUN/AppServer.


*Hi Michael,

You should not need to include the current directory (or any other
directory) in your classpath. There are several developers that are using
Windows with and without Netbeans w/o any problems. There is something else
wrong w/ your environment... it's not the build scripts in JSFTemplating.

Looking at the output you have below (which is not a regular "ant" or "ant
clean build" output... it appears to be an "ant all" output)... this line is
where things start to go wrong:
*

*Execute failed: java.io.IOException : CreateProcess: lib\ant\bin\ant.bat -f
aptbuild.xml -lib lib/external/ant-apt.jar compile error=2
*

*However, it doesn't stop at that point... it continues on and crashes
later. The reason it doesn't stop is because of how we used to invoke
"apt"... this has been changed, but the flag to stop hasn't been fixed. I
just fixed it now. This won't help fix your problem though... you still
need to figure out why it isn't invoking ant.bat for you.

You may have an older (or newer) version of ant that doesn't work correctly
(what version do you have?). It may be because the path contains spaces.
It may be because the path is too long. It may be because you have ant
environment variables set. It may be because "ant" isn't in your path.

When you find the reason, I will be happy to document it. However, I
haven't run into this problem before... maybe one of the other user's on
this list has. Anyone?

 *