Bug 120850 Import Jar with refactoring history: after import, jar should have new name
I20051214-0010 - export project JUnit to junit1.jar - copy junit1.jar into another project and add to build path - apply some refactorings to JUnit, then export with history to junit2.jar - import junit2.jar with Jar import wizard and choose to update junit1.jar => junit2.jar is copied into the project, but changes its name to junit1.jar. I would expect that the name of a jar is not changed, since it may contain version information which would be wrong after renaming. Rather, the classpath should be updated to the new name. Maybe, we even need a refactoring 'Rename Jar', which would also inform participants about the name change.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarimport/JarImportWizard.java
}
			}
		} finally {
			monitor.done();
		}
		return status;
	}
	/**
	 * Hook method which is called before the a refactoring of the history is
	 * executed. The refactoring itself is in an uninitialized state at the time
	 * of the method call. This implementation initializes the refactoring based
	 * on the refactoring arguments stored in the descriptor. All handles
	 * provided in the {@link RefactoringDescriptor#INPUT} or
	 * {@link RefactoringDescriptor#ELEMENT} attributes are converted to match
	 * the project layout of the client. This method may be called from non-UI
	 * threads.
	 * <p>
	 * Subclasses may extend this method to perform any special processing.
	 * </p>
	 * <p>
	 * Returning a status of severity {@link RefactoringStatus#FATAL} will
	 * terminate the execution of the refactorings.
	 * </p>
	 * 
	 * @param refactoring
	 *            the refactoring about to be executed
	 * @param descriptor
	 *            the refactoring descriptor
	 * @return a status describing the outcome of the initialization
	 */