Adding a New Path Defined Elsewhere to an SCM Package

[eshevin]

The above is the Synchronizer view between my Eclipse workspace and the destination SCM package for a Java code path added for a new project; this path doesn’t yet exist in the trunk.

 

We added the path in a package scheduled for an imminent release, but which still is not on the trunk.

 

Since then, a new package was created for a later promotion to the trunk, and that’s where we check in all our new code. All code changes that differ from the trunk, including those in the first package, have been added to the second package—except for the path above.

 

SCM refuses to add the path to the new package, with the message: “E03020689: Cannot create ...\network because it or its parent path already has a later trunk version or open branch exists.”

 

How can we get the artifacts above into the new package?

[Melinda Skelton]

This can happen when you have a new folder in one package, and files belonging to that new folder in a different package.  The package containing the files cannot be promoted until the package with the new folder is promoted first.  The reason is, the new folder doesn't officially "exist" in the next state until it is promoted there.  If the folder doesn't exist, it is not possible to promote the files.  No parent folder to which to anchor them.

 

There are a few options:

 

1. Promote the package containing the new folder first, or along with the other package containing the files for that folder.

2. Use the "Switch Package" process to move the folder to the package that must be promoted first.

3. Create a new empty package and use the "Switch Package" process to move the folder to the new package.  This will allow you to promote the folder structure first and any files inside the folder can be promoted when ready.

 

Let me know if this makes sense and if you need more details.

 

Thanks

Melinda Skelton

SCM Support Team