Sharing and Branching question

[jmarsch]

Queston:
(Using Vault 3.5.1)

I am having some problems with a share/branch in Vault. Basically, I have created a share, and now I can't get rid of it!

I am experimenting with how to manage multiple releases of an application. Things aren't going well.

I created a share on a folder:
-Framework

I shared to a temporary area, where I can play around a bit:
-Scratch
--Product
---Version 1.x
----Framework (shared)

I have 2 problems now.
1. I am ready to delete the shared folder under scratch -- I don't need it anymore. The operation keeps failing because there are files checked out (they were actually checked out before I ever created the share). I don't care. I want to abandon the share. I tried branching the shared folder, thinking that I could break the share and then delete the folder but the branch operation fails for the same reason (oddly, if I I branch from a non-shared folder that happens to have files checked out, the branch then delete works fine) (actually that only works sometimes, I have other posts out where the branch operation fails outright)

2. It appears that once you have shared a folder, you can never branch it to another folder
Here's what I mean. AFter I shared the folder at $/Framework (the root), the branch option for that folder changed. Now I can no longer branch this folder to $/Foo/Framework. I can only break the share that was created (which fails due to reasons in #1).

Here's what I think I need to do.

I have a multiple software products, and I have a shared library (framework).

I want to use the Trunk and branch pattern on the products, but they need to share the framework:
-Framework
--Trunk (shared)
--Version X (branch)

-Product1
--Trunk
---Code
---Framework (shared from framework trunk -- product trunk always uses the current framework code)
--Version 1
---Code (branched)
---Framework (branched -- product rev 1 frozen to specific framework version)


Given what I am running into with #2, I do not see how I can create a product trunk with the basic rule "always use the current framework code" because if I create a share on the framework trunk, then I can never branch the framework trunk.


Am I missing something on #1? is the only way to delete the share to first check everything in?

Am I missing something on #2 is there another way to attack the issue of multiple releases of multiple products that rely on shared code?

[Beth]

If the checkout occurred in the share and not the original folder, then you won't be able to delete it. If you have the check out occurring in the original folder, then you should be able to delete the share.

As for the Branch, try branching before you create the share and see if that works for you.

There were a few sharing fixes in Vault 3.5.2, but they may not be directly related to this. It's a free upgrade for you and faster anyway, so you might want to check it out. Here are the release notes for Vault 3.5.2.

[jmarsch]

Thanks Beth.

The checkout did occur in the original folder -- I didn't check anything out from the share.

On branching before I create the share, I don't think that this will work for me -- the share from the trunk will always exist, and at times we will need to create a branch to freeze on specific versions of the code.