> SVNKit might not be used in closed source projects, neither SVNKit
> forks might be closed source (unless SVNKit is licensed commercially).
that's sort of what i thought. most of the projects that sit in that forge.mil
repository are something called govt. open source ... which, i know, can s
Hello Brian,
> it's not clear to me, immediately, what rights i have to share their code
> without their permission ... and i guess it's not terribly clear what rights
> they have to keep me from sharing the code either. i will try to contact
> them and see how amenable they are to helping this c
thanks for the response, alexander
the extended svnkit library is a part of a project called Subversion-CAC that
links to this page: http://www.forge.mil/Resources-Subversion.html#svnkit
the irony is that the project site is CAC protected.
doing a quick comparison of the two libraries, it looks
Hello,
SVNKit from trunk does support MSCAPI certificates with a sort of a
"hack" - when prompted for SSL client certificate, user have to
specify MSCAPI;ALIAS string. Then SVNKit will use CAPI and SunMSCAPI
providers to load certificate - it will use Window-MY keystore when
SunMSCAPI provider is
greetings svnkit users,
i am a part of a fairly large team that just started using a CAC protected
TeamForge site and i am trying to determine the best way for our developers to
access the site. for the most part, we all use Eclipse which situates us
perfectly to take advantage of the CollabNe
