Xlink update

I never did a real research on it to see how to use. So, I think my problem was that I didn't create a branch to perform the change in the repository that my xlinks are linked to. I'll be in touch! You have to read this article, it will take 10 minutes and it will improve your daily work a lot!

I finally figured out how to work with xlink! It's awsome! But I still don't get why I cant update my xlink to the latest changeset in my parent repository. I mean, plastic did everything as promised: merged and created the branch in the parent repository.

The parent's repository maintainer approved my changes and decided to merge them in the parent's repository main branch. A new Baseline to everyone. How can I point my xlink to this new changeset that merged my changes and possible others changes? If I don't do it, I will have my changes, but not any other changes made by anyone in that project. Just today I was thinking about a folder structure to link my main project and other satellites projects like Mail Sender Project, Unit Of Work Pattern, Database Conventions Project and etc that I reuse a lot in some projects and I dont want to keep them in my main Project's main folder.

Then I decided to merge the changes in this new branch in Rep B in the main branch and some more changes made by other developers. My Rep A that has an xlink to Rep B has my changes, but not the new changes made in the "new release". There is a "-e" option in the Xlink command to do it, it allows you to change the target changeset to the latest RepB c. But I really recommend you to work integrating from the main repository RepA it's easier and more clear to understand, and also less work for the build master How is the proper way to use the -e parameter?

I tried it the day before yesterday and it did not worked to me. It was saying that I could not change the xlink. Did you understand my need? If I REALLY wanted to use an "component model design" for satellite libraries, I need to be able to change to make changes in the repository that has my libraries I my many projects and propagate them as BL as if the projects that use them were my clients.

It's ease to do if you have the power to change libraries but if in every project that uses the libraries could change like this, it would be a mess to maintain a BL to everyone. Good song!

In this moment there is no way to notify to the Main repository, the one that is having Xlinks to Libraries, the event "The Xlinked changeset have changed", obviously if you change your Library repository directly, if you do it using the Main repository it's going to work automatically, as I said before. You want for example create a Xlink to the cset "22" of your Library repository from your ProjectX repository, and then you or a co-worker of you create a new cset "23" directly on the Library repository.

You want that the Xlink stored in ProjectX rep pointing to Library rep updates itself to the new changeset created? Thanks for taking too much time with me on this, I just want to help you to build a even better xlink! Just to know if I understood you. So, as a user, you'll have to resolve any possible conflicts as you would with a normal "single repository" merge.

Now the merging of Form1. The answer is that the merge operation will also update the WXlink to point to the result of the merge in the MyLibrary repository. That is, as a result of the merge operation, there is a new version of Form1. For this reason, the Pending Changes view shows a pending merge link for the ProjectX repository, as depicted in the next figure:.

The overall result is that you only need to tell Plastic SCM "I want to merge this branch" in your workspace, and the merge operation will handle the changes made in wXlinked repositories. When Xlinks are replicated, the target they point to is still the original one.

So, say that you are replicating a repository with an xlink component1 pointing to changeset number 6 on repository MyLibrary on server mainserver. The destination of your replica is on another Plastic SCM server at otherserver. When you replicate the top-level repository, the Xlink in your replicated repository will still point to mainserver. If it is reachable from the location2. Most of the time, you'll want to replicate the MyLibrary repository to location2.

To tell the Xlink that you want to use the MyLibrary repository found in your default server that of the top-level repository , you need to create the Xlink with a relative server. This is achieved with the -rs modifier when the Xlink is created, as in the following example:.

When this link is replicated, it'll try to locate MyLibrary repository in the local server rather than mainserver. The Xlink will be pointing to the right changeset even if the number changes because it uses the changeset GUID rather than the changeset number to locate it. Read the Plastic SCM book to learn how replication works.

Xlinks guide What is an Xlink Projects often need to reuse existing components that have been developed and are actively used as part of other projects. An Xlink is defined with the following arguments: The directory entry to create in the current repository. This is a directory that will be used. The target repository.

The directory to mount in the target repository. You can Xlink to the root of another repository and any directory path inside by mounting a "subtree" on the parent repo as partial Xlinks. This directory must not exist already in the repository.

The xlink command will create an item for it, and it will throw an error if a file of the directory already existed with the same name. Together with the changeset it forms a changeset specification. In this case, there is no server specified. If the server is to be specified, the spec will look like this: 1 mylibrary servername It is also possible to specify a label instead of a changeset.

You'll note the new option in the Workspace Explorer context menu: Important : Partial Xlinks must be created only from the command line. The Xlink is created in the workspace and appears as a pending change in the Pending Changes View or cm status --added command , as shown here: Once it is checked in, the Xlink needs to be updated.

Do not hold the same line button down for 6 seconds as this will delete the current pairing. Dialing will start cell phone voice dialing. Each cell phone has its own line number 1, 2 or 3 has indicated by dots on the button it was paired to.

The XLink will automatically select which cell phone to use for outoing calls. While not necessasry, you can select which cell phone to use for an outgoing call. When you select a line and hear dial tone, you can proceed with your call. If you hear a series of rapid tones, it means that there is no cell phone currently connected to that line. Limitation of Liability. Governing Law. This Agreement shall be construed and enforced in accordance with the laws of the Province of Alberta.

No Assignment. Neither this Agreement nor any interest in this Agreement may be assigned by Licensee without the prior express written approval of Developer. Final Agreement. This Agreement terminates and supersedes all prior understandings or agreements on the subject matter hereof. This Agreement may be modified only by a further writing that is duly executed by both parties.