Menu ▾ ▴

#388 For external diff tools, compare selected versions always uses LATEST instead of selected version

2.x
closed-fixed
Thomas Bark
None
5
2021-09-02
2015-03-07
Andy Gianfagna
No

Please see bug #265. It may be related. The same issue still occurs with version 2.2.33.201308070746 when using an external diff tool. I have it setup to use Kdiff3 and I still see the problem. If it instead uses the built in eclipse diff, there it appears to work just fine, which appears to be fixed with $

Related

Bugs: #388

Discussion

  • Mikael Petterson

    Mikael Petterson - 2015-05-19

    I know I am late on this but do you have the possiblility to send a picture. I don't have access to clearcase anymore.

    //mike

     

  • Mikael Petterson

    Mikael Petterson - 2020-12-22
    • status: open --> open-accepted
    • assigned_to: Thomas Bark
     

  • Thomas Bark

    Thomas Bark - 2020-12-31

    Solved in 2.2.42.
    Please close ticket.

     

  • Mikael Petterson

    Mikael Petterson - 2021-01-04
    • status: open-accepted --> closed-fixed
     

  • Lidia Popescu

    Lidia Popescu - 2021-09-01

    Hello, I'm trying to understand why you made this change, because it causes issues on our side.
    If we check "Compare with external tool ", "Merge with external tool" and use bcompare v. 4.3.5 or lower. In external bcompare the differences between current updated file and compare with Change set predecessor, the changes are not visible, but inside eclipse the differences are visible.

    If I revert this commit, the problem is solved.
    9f0d4fc branch bug_388_extdiff merged

     

    • Thomas Bark

      Thomas Bark - 2021-09-01



      <meta name="viewport" content="width=device-width">
      <meta http-equiv="Content-Type" content="text/vnd.ui.insecure+html;charset=utf-8">

      Hi Lidia,
      Right now I'm In vacation in Maramures. So i cannot check the details.
      I did a mistake in latest version of the plugin. It's already solved on a branch, but not delivered as a new version.
      Please check my commits after last official delivery.
      Buna, Thomas

      --
      Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
      Am 01.09.21, 19:33 schrieb Lidia Popescu <lidochca@users.sourceforge.net>:


      Hello, I'm trying to understand why you made this change, because it causes issues on our side.
      If we check "Compare with external tool ", "Merge with external tool" and use bcompare v. 4.3.5 or lower. In external bcompare the differences between current updated file and compare with Change set predecessor, the changes are not visible, but inside eclipse the differences are visible.


      If I revert this commit, the problem is solved.
      9f0d4fc branch bug_388_extdiff merged



      [bugs:#388] For external diff tools, compare selected versions always uses LATEST instead of selected version


      Status: closed-fixed
      Group: 2.x
      Created: Sat Mar 07, 2015 12:53 AM UTC by Andy Gianfagna
      Last Updated: Mon Jan 04, 2021 06:15 AM UTC
      Owner: Thomas Bark


      Please see bug #265. It may be related. The same issue still occurs with version 2.2.33.201308070746 when using an external diff tool. I have it setup to use Kdiff3 and I still see the problem. If it instead uses the built in eclipse diff, there it appears to work just fine, which appears to be fixed with $



      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/eclipse-ccase/bugs/388/


      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/








       

      Related

      Bugs: #388

      • Lidia Popescu

        Lidia Popescu - 2021-09-02

        Thank you Thomas. Enjoy your trip in Maramures ;)

         

  • Lidia Popescu

    Lidia Popescu - 2021-09-01

    Suppose I made a change in a checked out file and would like to compare with Change Set Predecessor.

    With your change it compares same versions and it doesn't know about my changes that are not committed yet.
    bcompare \
    /${my_path_to_file}/MyFile.cpp@@/${my_view}/0 /${my_path_to_file}/MyFile.cpp@@/${my_view}/0

    the files are identical. If I make same comparison inside eclipse, it can see the differences.
    If I revert this commit, it compares current file with previous version and it works, the differences are found.
    bcompare \
    /${my_path_to_file}/MyFile.cpp
    /${my_path_to_file}/MyFile.cpp@@/${my_view}/0

    So, how to compare with bcompare when the changes are not committed yet ?
    Thank you
    Lidia

     

    Last edit: Lidia Popescu 2021-09-01

Log in to post a comment.