Problems with SVN plugin

[marfi]

Hi,
I've discovered few problems dealing with CL's SVN plugin. My project files are arranged in such way that header and implementation files are located in separated directories. CL project file is located in a directory with implementation files. If I want to commit my code via SVN plugin, I can choose whether I click onto relevant menu item in context menu of project or workspace tree item. The problem is following: If I use SVN commit from project tree item, only implementation files (*.cpp) are shown in commit dialog and changes made on headers files aren't commited. If I show SVN report from workspace's context menu then the report contains both implementation and header files, but after clicking onto "Commit All" link a commit dialog is displayed with no listed files thus the commit operation cannot be successfully finished.

Am I doing something wrong or is it a bug?

Regards
Michal

[eranif]

I am not sure why it is like that, since it is working properly for me, you may want to try to commit the SVN menu from the explorer tab (which also contains more options which are not available via the workspace view)
Eran

[marfi]

Hi, I've probably found the reason why it behaves so strange for me. My project and source files are located in separated directories with following structure:

Code: Select all

project root
    "build"
       Project.workspace
    "include"
       header files...
    "src"
       Project.project
       implementation files...

If I invoke SVN commit from the workspace's context menu then the SVN command is performed on the Project.workspace file (its directory) and neither source nor headers file are found in this (recursive) path. If I perform SVN commit via explorer panel on a topmost project directory, everything works fine. Likewise, If I invoke commit on project's context menu, only implementation files located along the project file are commited.

I understand that it is nearly impossible to found out what is the topmost project directory only from known location of project and workspace files, therefore It seems it is not the CL's bug but rather a feature...

Regards
Michal