I have been tasked with automating the build process for my current
project. This consists of a Java project containing common code, a Web
project, and an EJB project.
I have been working with the Ant / WSAD integration using the "Headless"
process. I have a build script that produces an .ear that I can
successfully deploy and run on a separate instance of WebSphere 4. This is
good.
My question is regarding behavior of the <projectBuild> task when there is
at least one compile error present. The <projectBuild> task is not failing
or terminating when there is a compile error present regardless of the
value of the "failonerror" attribute. I get a "BUILD SUCCESSFUL" message
after the task even though compile problems are noted in the trace. Is
this the expected behavior or am I somehow missing something?
<projectBuild ProjectName="${common_project}" failonerror="true"
DebugCompilation="false" BuildType="full" />
My ultimate goal is to implement a continuous integration loop (using a
product like CruiseControl). If the build doesn't fail when it has errors,
the continuous integration will be impossible to implement.
Thanks in advance for any insight.
Jon Culli
This transmission may contain information that is privileged, confidential and/or
exempt from disclosure under applicable law. If you are not the intended recipient,
you are hereby notified that any disclosure, copying, distribution, or use of the
information contained herein (including any reliance thereon) is STRICTLY PROHIBITED.
If you received this transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard copy format. Thank
you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
