Subversion svn:externals - What's wrong here?

Posted by Brandon Montgomery on Stack Overflow See other posts from Stack Overflow or by Brandon Montgomery
Published on 2010-03-01T15:44:12Z Indexed on 2010/04/01 3:03 UTC
Read the original article Hit count: 365

I first want to say I've read the Subversion manual. I've read this question. I've also read this question. Here's my dilemma.

Let's say I have 3 repositories laid out like this:

  • DataAccessObject/
    • branches/
    • tags/
    • trunk/
      • DataAccessObject/
      • DataAccessObjectTests/
  • PlanObject/
    • branches/
    • tags/
    • trunk/
      • PlanObject/
      • PlanObjectTests/
  • WinFormsPlanViewer/
    • branches/
    • tags/
    • trunk/
      • WinFormsPlanViewer/

The PlanObject and DataAccessObject repositories contain shared projects. They are used by the WinFormsPlanViewer, but also by several other projects in several other repositories.

Bear with me here. I put an svn:externals definition on the WinFormsPlanViewer/trunk folder like this:

https://server/svn/PlanObject/trunk Objects
https://server/svn/DataAccessObject/trunk Objects

And here's what I see after I do an svn update.

  • WinFormsPlanViewer/
    • branches/
    • tags/
    • trunk/
      • WinFormsPlanViewer/
      • Objects/
        • DataAccessObject/
        • DataAccessObjectTests/

The PlanObject stuff doesn't even come down in the update! I don't know if this has anything to do with it, but there's an externals definition on the PlanObject/trunk folder also:

https://server/svn/DataAccessObject/trunk Objects

What's going on here? What am I doing wrong? Are there bad consequences of referencing the PlanObject and the DataAccessObject from the WinFormsPlanViewer using svn:externals when the PlanObject references the DataAccessObject using svn:externals also?

© Stack Overflow or respective owner

Related posts about svn

Related posts about sharedobjects