Jump to content

Borja

Members
  • Content count

    41
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Borja

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, The left content should not be empty, isn't it? The left and right content should be always loaded. The encoding changed message doesn't change this. If the left content should not be empty, the issue will be downloading or reading the left content. Please, could you confirm if this is your situation? Could you send us the client logs? They should be located at C:\Users\<user_name>\AppData\Local\plastic4\logs Best regards, Borja
  2. Borja

    Problems with VS Add-in

    Hi, The error with the checkout, that has been moved locally, has been fixed. The fix will be available on the following release. Sorry for the inconvenience.
  3. Borja

    Moved detection

    Hi Søren, I have checked it with a similar case and it works correctly, as you can see: Xdiff example with just one move Xdiff example with several moves Can you send to us your files in order to try to reproduce your problem locally? We already use a variant of the Levensthein distance in order to detect the lines that have been moved. Regards
  4. Borja

    Linux sym links

    Hi, By default the operations are applied to the link target and not to the link itself. You can apply the operation to the link using the --symlink option on the command line. For example: cm ci /home/user/Pilot2.6/int/3rdParty/classpath-0.98/include/jni_md.h --symlink We are working on the symbolic links behaviour under Plastic SCM to make them easier to use. This new functionality will be published in a future release. The current public version does not support symbolic link officially. Regards Borja
  5. Borja

    Contributors = "None" ???

    The contributors "None" implies that source and destination have the same content than the common ancestor. This case may happen on different situations, such as: * You make a co on a branch and a ci forced, after that you merge the branch. In this case, the destination and the ancestor are the same revision, whereas the source and the ancestor has the same content because of ci forced. * You make a change on a branch and confirm it, after that you make another change to leave it with the same content of the beginning. In this case the destination and the ancestor are the same revision, whereas the source and the ancestor has the same content because you left the same content on it. There are other more complex situations where it can also happen, but at the end they can be reduced to these two cases. We are studding to change this behavior on next releases, to remove this kind of merge conflicts.
  6. Borja

    Security issues

    We have changed this extension for a new secured communication channel, that can be used as unique channel or at same time that the normal channel (unsecured channel). The channel is being using internally but it's not "officially released" yet, but it will be soon. Sorry for the inconveniences.
  7. Borja

    Filtering/Hidding branches

    Yes, it can be easily done using the attributes, which is a new feature included in Plastic SCM version 2.0. What you would have to do is create a new attribute named for example status: cm setattribute att:status br:/main/task1 closed Now, if you want to hide the old closed branches, you would only have to filter depending on the attribute status, asking for the
  8. Borja

    Evaluation / SQL Server

    Hi again Simon, Yes, sure. You can take a look at the user guide, which should give you a good overview on the system. Also consider the following papers: http://www.plasticscm.com/opsupport2.aspx The evaluation lasts for 30 days and 5 users. If you need an extended period just let me know. Also, what's your team size? Your development environment? Of course, don't hesitate to write us if you have any questions.
  9. Borja

    Evaluation / SQL Server

    Well, actually each repository is in a single database. The point is that Plastic keeps a list of all the existing repositories (which is another database) and also keeps track of the files you have on your local machine, which is the workspace database... Hope it is not a problem for you.
  10. Borja

    Evaluation / SQL Server

    Hi again Simon, Yes, it creates one database per repository plus one for workspaces plus one for the "repositories" database. So it will create at least 3 databases. Is it a problem? Regards,
  11. Borja

    Evaluation / SQL Server

    Hi Simon, I don't really understand your question. You can remove them if they're not going to be used and restart from a blank situation... Please let me know.
  12. Borja

    Evaluation / SQL Server

    Hi Simon, Yes, it is very simple. - You need to have a SQL Server (2005 or higher) installed. - Then create a db.conf file in your Plastic server directory. - The file contents should be: <DbConfig> <ProviderName>sqlserver</ProviderName> <ConnectionString>SERVER=YOURSERVER;User Id=YOUR USER;Pwd=YOUR PASSWORD;DATABASE={0};</ConnectionString> <DatabasePath>OPTIONAL PATH</DatabasePath> </DbConfig> - Then just restart the server If you have any issues or questions, please don't hesitate to contact again.
  13. Borja

    Change private items

    When you add a folder into the version control using the recursive option every file included on that folder is also added, so you do not have to add one by one! Do not worry about asking questions, that is what we are here for! Kind Regards,
  14. Borja

    Change private items

    Hi Simon, For adding any item into the version control you only have to right click on the item and press
  15. Borja

    Managing the Branches

    Well, normally our customers (and also ourselves internally) use some sort of task or issue tracking software (Bugzilla, Mantis, OnTime, defect control or even Jira). So the regular working model is: - You have an initial baseline - You create tasks and branches (one branch for each task, check http://www.plasticscm.com/whitepapers/bestpractices.pdf and also http://www.plasticscm.com/whitepapers/paralleldevelopment.pdf) - Developers work on their branches - Once they are done, tasks are marked as finished or closed (depending on the issue tracking software) - You *just* integrate the tasks which are closed... so you don't even have to "try to merge" your branches. - Alternatively you can also check the "branch explorer" diagram to check what's going on. Mixing standard and pro licenses is not possible (in fact one of the key differences between both releases is actually security).
×