Ojdeploy sometimes generates invalid JARs

Question

We've encountered the following problem: sometimes ojdeploy (called via ant task) generates invalid JARs for some projects in the workspace. Invalid means they have a size less the 1KB, there may be only META-INF\manifest.mf and no classes at all inside that JAR, or there may be some (not all) classes. And consequently the whole build fails because of "package blah-blah-blah does not exist" etc.
Here's the bit of example from the failed build (some parts of the log are obscured and skipped):
     [exec] 13.04.2011 17:31:48 oracle.ide.boot.Launcher throttleLocale
     [exec] INFO: Locale ru_RU is not supported by this product. Forcing locale to en_US.
     [exec] ----build file----
     [exec] <?xml version = '1.0' standalone = 'yes'?>
     [exec] <ojdeploy-build>
     [exec]     <deploy>
     [exec]         <parameter name="workspace" value="${workspace}\"/>
     [exec]         <parameter name="project" value="${project}"/>
     [exec]     </deploy>
     [exec]   <defaults>
     [exec]     <variable name="workspace" value="our workspace"/>
     [exec]     <variable name="project" value="BlahBlahBlah"/>
     [exec]     <parameter name="buildfile" value="our buildfile"/>
     [exec]     <parameter name="profile" value="*"/>
     [exec]     <parameter name="clean"/>
     [exec]   </defaults>
     [exec] </ojdeploy-build>
     [exec] ------------------
... skipped ...
     [exec] [5:32:00 PM] Clean completed.
     [exec] Compiling...
     [exec] Context: selection=BlahBlahBlah.jpr application=BlahBlahBlah.jws project=BlahBlahBlah.jpr node=BlahBlahBlah.jpr
     [exec]
     [exec] C:\Oracle\Middleware\jdk160_14_R27.6.5-32\bin\javac
     [exec] -g
     [exec] -Xlint:all
... skipped ...    
     [exec] Compiling 4 sources
     [exec]   Compiling ...Logger.java
     [exec]   Compiling ...SystemOutHandler.java
     [exec]   Compiling ...LogFormatter.java
     [exec]   Compiling ...LoggerFactory.java
     [exec]   Writing ...Logger$CSIntFormatter.class
     [exec]   Writing ...Logger.class
     [exec] Apr 13, 2011 5:32:02 PM oracle.jdevimpl.deploy.common.ModulePackagerImpl deployProfiles
     [exec] INFO: Deploying profile...
     [exec]
     [exec] Apr 13, 2011 5:32:02 PM oracle.jdeveloper.deploy.jar.ArchiveDeployer logFileWritten
     [exec] INFO: Wrote Archive Module to file:/...Logging.jar
     [exec] Apr 13, 2011 5:32:02 PM oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl$DeployConsoleLogger finished
     [exec] INFO: Elapsed time for deployment:  2 seconds
     [exec]
     [exec] Apr 13, 2011 5:32:02 PM oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl$DeployConsoleLogger finished
     [exec] INFO: ----  Deployment finished.  ----
     [exec]
     [exec]   Writing ...SystemOutHandler.class
     [exec]   Writing ...LogFormatter.class
     [exec]   Writing ...LoggerFactory.class
     [exec] [5:32:02 PM] Successful compilation: 0 errors, 0 warnings.BTW, I've noticed one strange thing while writing this. I see that ojdeploy says " Deploying profile... Wrote Archive Module to file:/...Logging.jar..." and <b>AFTER having created the JAR</b> it says "Writing ...SystemOutHandler.class Writing ...LogFormatter.class Writing ...LoggerFactory.class"
Has anyone encountered such strange behavior of ojdeploy?

Answer 1

(kinda bump)
I haven't mentioned that we use JDeveloper 11.1.1.2