CollabNet Subversion update

About Mark Phippard

Engineering manager for several teams at CollabNet, including CloudForge, Subversion, Subversion Edge, Git and our Desktops and Integrations. Project owner for the Subclipse project, which provides Subversion support in Eclipse. Also a full committer for the Subversion project. Product owner for GitEye, Subversion Edge and the CollabNet Desktops and Integrations.

  4 comments for “CollabNet Subversion update

  1. Jon
    May 18, 2007 at 4:17 pm

    Any chance of compiling the windows version against Apache 2.2 instead of 2.0? Its about time…

  2. May 18, 2007 at 4:19 pm

    It is on the to-do list. Perhaps when we get to the 1.5.0 releases.
    Mark

  3. May 21, 2007 at 12:03 pm

    If you’re switching away from the java based installer, I wouldn’t go for NSIS but use WiX ( http://wix.sourceforge.net ) instead. My guess is that you’re targeting corporate users with your binary packages, and for those you should use msi installers.
    Especially on Vista, you won’t have much less problems (hint: UAC) with an msi than with an exe installer like NSIS.
    Yes, the learning curve for WiX is a little bit higher than for NSIS, but it’s worth it.

  4. March 11, 2008 at 8:02 pm

    I have a working version of the wix installer, I’m just polishing it up before presenting to the dev’s. Should be able to have apache version selection in the one installer.
    BTW, I’m the current installer maintainer; using wix should make the build process more intuitive. Ultimately I’d like to unify the build into wix instead of having the separate perl scripts, however this may not be possible. I’m using SharpDevelop as a wix project editor.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

CAPTCHA Image

*