PM26111: Rational Application Developer v7.5.5.2 Headless Ant runAnt.bat returns exit code (== ERRORLEVEL) = 0

Rational Application Developer for WebSphere Software, Version 7.5.5.3

APAR status

• Closed as program error.

Error description

• RAD v7.5.5.2 Headless Ant runAnt.bat always returns exit code
  (== Windows ERRORLEVEL) = 0, even on ant task failure
  
  Problem
  
  RAD v7.5.5.2 Windows or Linux,
  Headless Ant runAnt.bat always returns
  exit code (== ERRORLEVEL) = 0 ,
  even on failure of any ant task and
  build shows BUILD FAILED.
  Also in RAD v8.0
  
  
  
  For example, guaranteed to fail simple build.xml
  
  //---f ile: build.xml
  <project name='x' default='a'>
    <target name='a'>
      <fail/>
    </target>
  </project>
  //---
  
  and runAnt.bat returns an ERRORLEVEL of 0 ( ==zero), even though
  there is an obvious failure.
  I had runAnt.bat echo ERROERLEVEL after JAVAEXE ...
  
  In RAD v7.0.0.10 this returns ERRORLEVEL=13, as expected
  
  
  Confirmed also using a a bat file to invoke runAnt.bat to check
  it
  //-- runAntInvoker.bat
  @echo off
  echo 'BOBD runAntInvoker.bat...calling runAnt.bat'
  call runAnt.bat
  echo 'BOBD runAntInvoker...done runAntbat, return exit code'
  echo Exit Code = %ERRORLEVEL%
  //--
  
  Example customer scenario was:
  When 'projectSetImport' fails due to incorrect CVS credentials,
  the
  'runAnt.bat' returns exit-code of 0, as if everything's OK.
  There's a
  check in 'runAnt.bat' against various exit-codes of the runAnt
  JVM,
  but that exit code is always 0.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Java Return codes from headless builds are not being
  properly set
  

Problem conclusion

• Extra debugging code injected by mistake in Rational
  Application Developer v7.5.5.2 is causing this. Problem
  fixed in Rational Application Developer v7.5.5.3
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL APP DEV WI

• Fixed component ID

  5724J1901

Applicable component levels

• R755 PSN

     UP