jberet hangs if the partition plan defines the number of threads as 0

Jberet hangs if the getThreads call of the partition plan returns 0.

The library hangs in StepExecutionRunner (around line 288)

          if (i >= numOfThreads) {
                completedPartitionThreads.take();
          }

The maven project attached shows the difference between RI and jberet

The javadoc says for PartitionPlan::getThreads

Gets maximum number of threads requested to use to run partitions for this step. A value of '0' requests the batch implementation to use the partition count as the thread count. Note the batch runtime is not required to use * this full number of threads; it may not have this many available, and may use less.