Login | Register
My pages Projects Community openCollabNet

Discussions > issues > [Issue 1630] New - SVN Externals property applied to wrong project

subclipse
Discussion topic

Back to topic list

[Issue 1630] New - SVN Externals property applied to wrong project

Author pjede
Full name Pieter van Ede
Date 2015-05-22 08:36:58 PDT
Message http://subclipse.tig​ris.org/issues/show_​bug.cgi?id=1630
                 Issue #|1630
                 Summary|SVN Externals property applied to wrong project
               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|pjede






------- Additional comments from pjede at tigris dot org Fri May 22 08:36:57 -0700 2015 -------
I have troubles with a very disturbing bug that makes me apply my SVN Externals
Property to the wrong project in Eclipse.

You can reproduce the problem with the following setup:

Make sure you have projects foo, bar and zoomer (the names are important because
alphabetic ordering seems the problem with this bug). Foo and bar are normal
Java projects, zoomer is just needed for the externals definition.
In the project zoomer, you define svn-externals property so that it includes foo
and bar at toplevel.

Now you perform a simple SVN Checkout of the project zoomer. Here zoomer should
be checkout out as a project and not configured via new project wizard.

You should have the following folder structure in your workspace:

zoomer
|- bar
|- foo

And only zoomer is listed as a project in your Java perspective. Now you import
existing projects and choose the zoomer directory from your disk and check 'scan
for nested projects'. Eclipse finds bar and foo and lets you import those projects.

Now your Java perspective lists bar, foo and zoomer in that order.
On the projects zoomer you can view the SVN properties and see the svn:externals
property. Foo and bar have no svn properties.

Now edit the svn properties on project zoomer. When you hit OK, the properties
of zoomer remain unchanged. However, project bar now magically has the updated
properties you wanted for zoomer. You can also see this in the SVN Console.

This is very annoying, because in my organization we are trying to improve our
build system. This bugs has two major drawbacks:

- users cannot edit svn-externals from within Eclipse
- when users have accidentally triggered this bug, SVN Update will apply the
externals definition to bar. We have over 30 projects that we aggregate, and you
can see that this is time consuming when eclipse suddenly hogs your workspace
with several 100's MB.

I hope you can resolve this, or point me to a workaround. I have reproduced this
issue with Subclipse 1.6.x and 1.10.x with both JavaHL and SVNKit.

If you need more details, please let me know.

« Previous message in topic | 1 of 1 | Next message in topic »

Messages

Show all messages in topic

[Issue 1630] New - SVN Externals property applied to wrong project pjede Pieter van Ede 2015-05-22 08:36:58 PDT
Messages per page: