You must add VCS project nature to the packages that are not created in the local Integration Server but are available in the VCS if you want to copy or move these packages to Integration Server. To do this, right-click the package in the Package Explorer view and select Configure > Convert to Local Service Development Project. This also adds the Java project nature to the package.

If you are using Team Foundation Server as your VCS client, the workspace of the local service development project is set to the Integration Server_directory \instances\default\packages directory. When you check out a package, it is added to the Integration Server_directory \instances\default\packages directory. Hence, you will not see the Move Project to IS Package option described below. However, you can load the package in the Integration Server_directory \instances\default\packages directory by right-clicking the package in Package Explorer view and selecting Load IS Package. After you load the package, the Load IS Package option will change to Reload IS Package.

If you are using EGit as your VCS client, select Move project to Integration Server package as linked resource to set the workspace of the local service development project to any directory on your system and check out packages to that directory.

If a package with the same name already exists in the Integration Server_directory \instances\default\packages directory, the behavior of Designer depends on your VCS client:

If you are using Team Foundation Server as your VCS client, Designer will merge the contents of the two packages.

If you are using CVS or SVN as your VCS client, Designer will replace the existing package with the package from the VCS repository.

Designer automatically builds the Java and C/C++ services when you move the associated project to the Integration Server_directory \instances\default\packages directory, if you have the Build Automatically workspace preference (Project > Build Automatically) selected.