RESOLVED - issue BATCH-158: Dependency cycle between execution.step and execution.step.simple

http://opensource.atlassian.com/projects/spring/browse/BATCH-158

StepConfiguration had to pick up an extra flag in the interface, and the configuration implementations had to be separate from the executor implementations.

Also fixed a cycle in core (JobIdentifier is part of domain).

core/src/main/java/org/springframework/batch/core/runtime/JobIdentifier.java

@@ -1,40 +0,0 @@
-/*
- * Copyright 2006-2007 the original author or authors.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *      http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-package org.springframework.batch.core.runtime;
-
-import org.springframework.batch.core.domain.JobInstance;
-
-/**
- * Identifier strategy for {@link JobInstance}. Different batch projects can
- * have different approaches and requirements regarding the identity of a job.
- * The minimum requirement is to provide a unique name to identify a job. Other
- * applications or projects might add other properties like a schedule date, or
- * an additional label (code).
- * 
- * @author Dave Syer
- * 
- */
-public interface JobIdentifier {
-
-	/**
-	 * A name property for jobs provided by the {@link JobIdentifier} strategy.
-	 * 
-	 * @return the name of the job
-	 */
-	public String getName();
-
-}