Details

    • Type: Wish Wish
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Component/s: None
    • Labels:
      None

      Description

      Corporate firewalls usually block cvs/svn access. Downloading lots of source files via the browser is not an option.
      I suggest you provide a browser-downloadable snapshot of the trunc on
      http://directory.apache.org/community%26resources/sources.html

      as on http://www.jacorb.org/download.html

        Issue Links

          Activity

          Hide
          Emmanuel Lecharny added a comment -

          note : Moved to the DIR project, as it's not a Directory Server specific issue.

          We might consider to proivide such tar to users. Not exactly a bad idea, as it saves bandwith ...

          Show
          Emmanuel Lecharny added a comment - note : Moved to the DIR project, as it's not a Directory Server specific issue. We might consider to proivide such tar to users. Not exactly a bad idea, as it saves bandwith ...
          Hide
          Emmanuel Lecharny added a comment -

          There are some things to consider :

          • should we provide a jars for every tagged version ?
          • should we generate a daily tar of the trunk ?

          I think that having a source tarball of the tagged version + the associated Javadocs is important.

          Show
          Emmanuel Lecharny added a comment - There are some things to consider : should we provide a jars for every tagged version ? should we generate a daily tar of the trunk ? I think that having a source tarball of the tagged version + the associated Javadocs is important.
          Hide
          Felix Knecht added a comment -
          • Tagged versions +1
          • Daily -1 (and where should it be placed)

          BTW:
          I thought that exactly this is one of the advantages of svn. It uses normally http protocol on port 80 (443) instead of something specific as cvs. Why/How should it be blocked by corporate firewalls when 'normal' browing is allowed?

          Show
          Felix Knecht added a comment - Tagged versions +1 Daily -1 (and where should it be placed) BTW: I thought that exactly this is one of the advantages of svn. It uses normally http protocol on port 80 (443) instead of something specific as cvs. Why/How should it be blocked by corporate firewalls when 'normal' browing is allowed?
          Hide
          Jürgen Weber added a comment -

          Looks like a default Squid configuration does not let svn through:

          http://www.mikepot.com/1544.html
          "Squid had to be convinced it was ok to accept a few extra http commands:
          extension_methods REPORT MERGE MKACTIVITY CHECKOUT"

          My firewall admin certainly won't open that.

          Show
          Jürgen Weber added a comment - Looks like a default Squid configuration does not let svn through: http://www.mikepot.com/1544.html "Squid had to be convinced it was ok to accept a few extra http commands: extension_methods REPORT MERGE MKACTIVITY CHECKOUT" My firewall admin certainly won't open that.
          Hide
          Felix Knecht added a comment -

          Did you tried using https instead of http? IIRC you don't need an account just to checkout code using https
          -> svn co https://svn.apache.org/repos/asf/directory/apacheds/trunk/ e.g.

          I'm not sure if it helps, but squid shouldn't be able this way to recognize svn content.

          Show
          Felix Knecht added a comment - Did you tried using https instead of http? IIRC you don't need an account just to checkout code using https -> svn co https://svn.apache.org/repos/asf/directory/apacheds/trunk/ e.g. I'm not sure if it helps, but squid shouldn't be able this way to recognize svn content.
          Hide
          Emmanuel Lecharny added a comment -

          We already provide a source package for tagged version, it's too complex and costly to do the same for trunk, as we have around 10 commits a day.

          Sorry for those who are working in an company blocking SVN :/

          Show
          Emmanuel Lecharny added a comment - We already provide a source package for tagged version, it's too complex and costly to do the same for trunk, as we have around 10 commits a day. Sorry for those who are working in an company blocking SVN :/

            People

            • Assignee:
              Unassigned
              Reporter:
              Jürgen Weber
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development