MadCap Central
MadCap Contributor
MadCap Analyzer
MadCap Lingo
MadCap Mimic
MadCap Capture
MadCap Pulse
MadCap Doc-To-Help
Knowledge Base
That’s right, not only does MadCap Flare support Team Foundation Server (TFS) and Visual Source Safe (VSS), it also supports Subversion (SVN), without the need to install any third-party plug-ins.
Click to see a demo
SVN is one of the most widely used source control solutions — it is free and can run on almost any platform. With Flare 7, you no longer need a third-party plug-in to take advantage of integrated source control and SVN.
Now you can use SVN as a provider when binding an existing project to source control, creating a new project, and importing a project from source control. Take advantage of all of the source control features that are built in to Flare, such as checking files in or out, or getting the latest version of source control files.
To read more about Subversion and Flare 7, read this blog post from Laura Johnson:
Flare v7 is Here – Cue Angels and Choir!
About Jose Sermeno
With over 10 years of experience in the software industry, Mr. Sermeno brings a wealth of knowledge and expertise to the product evangelist team, helping introduce new users to everything MadCap Software. In his spare time, Jose is the Project Director for San Diego City Robotics, the San Diego community college systems robotics program, and enjoys working in software design and open source hardware development. Prior to joining MadCap in late 2010, Jose ran a Drupal development shop, and was an application manager for Temple University Health System.
Last Modified: July 15, 2013
This entry was posted in MadCap Flare, MadCap Software, Tech Comm, Tips & Tricks. Bookmark the permalink.
is it possible to override or customise the SVN comments, our projects use Pre-Commit validation to ensure the comment Prefix is of a particular format relating to our issue tracking database?
p.s. The link is broken http://flareforhelp.lauracjohnson.com/2011/03/flare-v7-is-here-cue-angels-and-choir/
Yes, when you check in the file(s) from Flare you have the opportunity to enter any comment at that time.
Thanks for the note regarding the Flare for Help link. Its fixed and currently points to: http://www.flareforhelp.com/2011/03/flare-v7-is-here-cue-angels-and-choir/
For more information on using Source Control with Flare, see the linked article here: https://help.madcapsoftware.com/flare9/Default.htm#Source_Control/About_Source_Control_and_Multi_Authoring.htm?Highlight=comment
Unfortunately I can not find a way to bind the project to SVN without it using its own comments in the format of “Adding Folder c:\svnrepo” etc so each time I try and either create a new project or bind an existing one it fails the SVN part due to the strict comments format on our SVN Repo?
Any further advice is appreciated, maybe there is no workaround and this need logging as an enhancement request to allow custom comments during the binding process screens.
Theres not a comment entry dialog on the initial bind (even though SVN supports it) from the Flare side. I’ve added this as an enhancement suggestion (#77795) on the Source Control functionality with SVN. Thanks for identifying the issue. You’ll receive an email when this is addressed in the future.
Sorry for digging up this old topic , but I am in a dire situation now . I am stuck with Flare 7 and trying to bind my project to svn using Flare’s in built mechanism . I could not get the binding done no matter what I do .
I have selected provider as Subversion and in the “Server” field givenlike this
https://my.svn.server/svn/MyRepo:80
Project path : https://my.svn.server/svn/MyRepo/module
Getting a ssl hand shake error when i click browse button.
SSL Handshake failed: SSL error code: 1/1336032856 ( https://my.svn.server)
Any idea about this ?
Looking online I found this thread. This might help you in resolving the error.
This can happen when the hostname reported by the server does not the match hostname given in the SSL certificate. Make sure your server configuration uses correct values for ServerName and NameVirtualHost.
source: http://subversion.apache.org/faq#ssl-error-336032856