Login | Register
My pages Projects Community openCollabNet

Discussions > issues > [Issue 1646] New - Synchronize and Update of a new Directory with new Files failed

subclipse
Discussion topic

Hide all messages in topic

All messages in topic

[Issue 1646] Synchronize and Update of a new Directory with new Files failed

Author selsemore
Full name Stephen Elsemore
Date 2016-02-22 05:26:52 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=1646



User selsemore changed the following:

                What |Old value |New value
====================​====================​====================​====================​
                  Status|NEW |RESOLVED
--------------------​--------------------​--------------------​--------------------​
              Resolution| |FIXED
--------------------​--------------------​--------------------​--------------------​




------- Additional comments from selsemore at tigris dot org Mon Feb 22 05:26:52 -0800 2016 -------
I made a fix so that the sync view will now show children of incoming folder additions. Closing
this, but it can be reopened if a scenario is identified in which updating a folder brings it in as
depth=empty.

[Issue 1646] Synchronize and Update of a new Directory with new Files failed

Author selsemore
Full name Stephen Elsemore
Date 2016-02-19 10:15:44 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=1646






------- Additional comments from selsemore at tigris dot org Fri Feb 19 10:15:42 -0800 2016 -------
I did experiment with trying to find a way that updating could bring a folder in as depth=empty.
I tried updating at various levels, updating folders with property changes, etc. I couldn't find
any scenario that caused this to happen, except for using the "Update to version..." option and
explicitly selecting that level. If anybody discovers a recipe for such a problem, please post it.

Maybe we can revisit the feasibility of showing the children of the new folder in the synch view.
I do notice that from the command line 'svn status -u' does include them (I wonder if this has
always been the case).

[Issue 1646] Synchronize and Update of a new Directory with new Files failed

Author marcmuel
Full name Marcus Müller
Date 2016-02-19 09:27:04 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=1646



User marcmuel changed the following:

                What |Old value |New value
====================​====================​====================​====================​
                      CC|'selsemore,zagser168' |'markphip,selsemore,zagser
                        | |168'
--------------------​--------------------​--------------------​--------------------​




------- Additional comments from marcmuel at tigris dot org Fri Feb 19 09:27:04 -0800 2016 -------
Hi Mark.
I understand that I can't update a file to a non existent folder in my
workingcopy. But when I synchronize my project with HEAD I have to see all
changes.

If the Team Synchronize View shows new files in a new folder it can decide what
the update command has to do. Update-command can show an explaining message or
update the folder with the file automatically. But showing only the folder is
very confusing.

[Issue 1646] Synchronize and Update of a new Directory with new Files failed

Author markphip
Full name Mark Phippard
Date 2016-02-19 09:06:55 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=1646






------- Additional comments from markphip at tigris dot org Fri Feb 19 09:06:30 -0800 2016 -------
What Steve means is you cannot update a file without also having its containing folder. So since you do not
have the folder at all, you just see the folder as an incoming change and it is assumed you will get anything
beneath it too.

We do need to make sure that there is not some scenario where updating the folder brings it in as
depth=empty.

Generally, we tend to update from the root of our project so just do not run into things like this.

[Issue 1646] Synchronize and Update of a new Directory with new Files failed

Author marcmuel
Full name Marcus Müller
Date 2016-02-19 09:01:59 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=1646



User marcmuel changed the following:

                What |Old value |New value
====================​====================​====================​====================​
                      CC|'zagser168' |'selsemore,zagser168'
--------------------​--------------------​--------------------​--------------------​




------- Additional comments from marcmuel at tigris dot org Fri Feb 19 09:01:59 -0800 2016 -------
Thank you Stephen for answer.

I think you right. With the function "Team->Update to version" I'm able to solve
the problem. But I think the real defect is that the folder after the checkout has
the wrong depth.

Your statement why the new files doesn't listed in the Team Synchronize View
doesn't match my situation because all elements was versioned in svn. The commit
with revision 14449 contains all together. The files and the folder.

[Issue 1646] Synchronize and Update of a new Directory with new Files failed

Author selsemore
Full name Stephen Elsemore
Date 2016-02-19 03:20:32 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=1646






------- Additional comments from selsemore at tigris dot org Fri Feb 19 03:20:32 -0800 2016 -------
If the working copy depth is set to something, then update, by default, will use the same
depth (as it should). If you want to override/change the depth that your working copy has
previously been set to, you can do so:

Team->Update to version...
Select the depth you want in the Depth dropdown.
Check "Change working copy to specified depth"

As for why synchronize shows only the new folder and not its contents, this is by design.
Even if the files were shown, there would be little that you could do with them as their
parent is not yet versioned.

[Issue 1646] Synchronize and Update of a new Directory with new Files failed

Author zagser168
Full name ZagSer168
Date 2016-02-18 23:55:07 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=1646



User zagser168 changed the following:

                What |Old value |New value
====================​====================​====================​====================​
                      CC|'' |'zagser168'
--------------------​--------------------​--------------------​--------------------​




------- Additional comments from zagser168 at tigris dot org Thu Feb 18 23:54:56 -0800 2016 -------
1

[Issue 1646] New - Synchronize and Update of a new Directory with new Files failed

Author marcmuel
Full name Marcus Müller
Date 2016-02-18 09:08:44 PST
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=1646
                 Issue #|1646
                 Summary|Synchronize and Update of a new Directory with new Fil
                        |es failed
               Component|subclipse
                 Version|current
                Platform|All
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P1
            Subcomponent|core
             Assigned to|issues@subclipse
             Reported by|marcmuel






------- Additional comments from marcmuel at tigris dot org Thu Feb 18 09:08:32 -0800 2016 -------
Subclipse version: 1.10.11
Eclipse: Mars (4.5)

In my case the new Workspace-Folder WWS_DEV/WwsVersand/User with 4 new files
inside was committed by a co-worker.

After a Synchronize on the whole Project I can see only the Folder
WWS_DEV/WwsVersand/User as an incoming change. The new file wasn’t listed. If I
open “SVN Repository Exploring” I can see that these files are really committed
to the repository with the revision 14449.

I’ve made an update to the changeset and following update-command was reported:

update C:/XXX/WWS_DEV/WwsVersand/User -r 14449 --depth=empty --force
    A C:/XXX/WWS_DEV/WwsVersand/User
    Updated to revision 14449.
    ===== File Statistics: =====
    Added: 1

As expected the 4 new files wasn’t updated. Only the folder was created. In this
Situation I have no chance to get these files with Subclipse.

I had to update the files with the svn client directly. But when I tried this I
found another problem. I tried to update the content of the folder:

c:\XXX\WWS_DEV\Ww​sVersand\User>sv​n up
Aktualisiere ».«:
Revision 14449.

The files won’t come. Second try:

c:\XXX\WWS_DEV\Ww​sVersand\User>sv​n up --depth=files
Aktualisiere ».«:
Revision 14449.


The same result. No files in my working copy.

I issued the svn info command and found the solution:


c:\_XXX\WWS_DEV\W​wsVersand\User>s​vn info
Pfad: .
Wurzelpfad der Arbeitskopie: C:\XXX\WWS_DEV
URL: http://john:8888/svn​/WWS-Repository/trun​k/WWS/WwsVersand/Use​r
Relative URL: ^/trunk/WWS/WwsVersand/User
Basis des Projektarchivs: http://xxx:8888/svn/​WWS-Repository
UUID des Projektarchivs: d8a95d6f-5a14-664c-a​d31-e6effe1ca67f
Revision: 14449
Knotentyp: Verzeichnis
Plan: normal
Tiefe: »empty«
Letzter Autor: sp
Letzte geänderte Rev: 14449
Letztes Änderungsdatum: 2016-02-18 15:07:26 +0100 (Do, 18. Feb 2016)

The depth-Property (German=Tiefe) of the directory stands on »empty«. So I tried
the following command:

c:\XXX\WWS_DEV\Ww​sVersand\User>sv​n up --set-depth=files
Aktualisiere ».«:
A VersandartChangeUI.java
A VersandartChangeView.java
A VersandartChangeViewCtl.java
A VersandartChangeView​SearchKey.java
Aktualisiert zu Revision 14449.

Now the depth-Property of the directory is correct again and the missing files
are updated.


So we have two Problems:

a) Why the files not shown in the Team Synchronize View?

b) The update on new directories with the –depth=empty option persists this
option as Folder-Property.

Solution:

a) I don’t know???

b) The update-command should use the additional option –set-depth=infinity.
Then the folder will take the expected default-value for the depth-Property.
Messages per page: