#3027 Validate SVN checkout url if it's changed

v1.0.0
closed
nobody
SCM
Cory Johns
2015-08-20
2011-10-18
No

If a user changes the default SVN checkout url, should we validate that the path actually exists?

Related

Tickets: #3027
Tickets: #4300
Tickets: #4592
Tickets: #4770

Discussion

  • Anonymous - 2011-10-27

    Originally by: sakaal

    In my project(s) I will need SVN repositories that contain multiple modules, each with their own trunks. An example repository layout would look like this:

    /
        module1/
            branches/
            tags/
            trunk/
                pom.xml
    
        module2/
            branches/
            tags/
            trunk/
                pom.xml
    
        module3/
            branches/
            tags/
            trunk/
                pom.xml
    
        trunks/
            pom.xml
    

    When working with Eclipse and Maven, sometimes I also create this /trunks directory at the repository root. Then I use "svn propset" to set the "svn:externals" property for /trunks such that checking out /trunks will automatically checkout all the module trunks under it. See svn:externals in Subversion documentation.

    Suppose the user has checked out https://svn.example.com/group/project/trunks to ~/workspace/project

    Now, the svn:externals would look like this:

    user@host:~$ svn propget svn:externals workspace/project
    module1 https://svn.example.com/group/project/module1/trunk
    module2 https://svn.example.com/group/project/module2/trunk
    module3 https://svn.example.com/group/project/module3/trunk
    

    This allows me to create a Maven parent project pom.xml in the /trunks directory with all its modules checked out from separate trunks.

    This is how I can implement separate versioning scheme for all the modules within the same repository.

    When using a repository layout like this, I would like to set the default checkout URL to: https://svn.example.com/group/project/trunks

    Using that URL the user would get the hierarchical Maven project checked out correctly.

     
  • Anonymous - 2011-10-28

    Originally by: sakaal

    I forgot to add that also the checkout local target directory name should be configurable.

    My SF.net project name is "agora-exchange" because "agora" was already taken. The default SVN checkout destination for my "site" module is "agora-exchange-site". However, I would like to advertise "agora-site" as the default checkout local target name.

    Please let the user decide how to advertise their SVN repositories. Your defaults do not work well in many cases.

    svn co https://svn.example.com/group/project/trunks myproject
    

    I would like to be able to customize both "trunks" and "myproject" above to any reasonable path name.

     
  • Dave Brondsema

    Dave Brondsema - 2011-11-01

    I know it doesn't address your full request, but you can customize the 'trunks' portion of the checkout URL. If you go to Admin, then Tools, then click on "Checkout URL" for the tool.

     
  • Mark Ramm - 2012-01-12
    • milestone: limbo --> forge-backlog
     
  • Dave Brondsema

    Dave Brondsema - 2012-05-31
    • labels: --> migration
     
  • Dave Brondsema

    Dave Brondsema - 2012-05-31

    Also, in the project upgrade code, after an SVN repo is imported we should remove the 'trunk' from the default checkout URL if there is not a trunk dir.

     
  • Dave Brondsema

    Dave Brondsema - 2012-08-29
    • size: --> 2
     
  • Dave Brondsema

    Dave Brondsema - 2012-09-07
    • milestone: forge-backlog --> forge-sep-21
     
  • Dave Brondsema

    Dave Brondsema - 2012-09-10
    • labels: migration --> migration, 42cc
     
  • Dave Brondsema

    Dave Brondsema - 2012-09-10
    • milestone: forge-sep-21 --> forge-backlog
     
  • Igor Bondarenko - 2012-09-11

    Created #165: [#3027] Validate SVN checkout url if it's changed (2cp)

    • status: open --> in-progress
     

    Related

    Tickets: #3027

  • Igor Bondarenko - 2012-09-14

    Closed #165. Branch 42cc_3027.

    • status: in-progress --> code-review
     
  • Dave Brondsema

    Dave Brondsema - 2012-09-17
    • qa: Cory Johns
     
  • Cory Johns - 2012-09-18
    • status: code-review --> closed
    • milestone: forge-backlog --> forge-sep-21
     
  • Dave Brondsema

    Dave Brondsema - 2012-09-21
    • size: 2 --> 0
     

Log in to post a comment.