Some commands can work more relaible with the usage of JavaHL for windows.
there are some known alternatives to the currently used cmd line client
- svnkit (javasvn)
each one brings its own specific issues (deployment, licensing, etc.), but it is
to reconsider if we could use or at least support them in the future.
*** Issue 89497 has been marked as a duplicate of this issue. ***
In the comments for 89497 it's mentioned that SNVKit can not be used as part of
Netbeans because of license issues. Can somebody please elaborate what this
means? Other open source projects use it, even Hudson uses it, but somebody in
that other issue commented specifically that their license was incompatible with
the one used by Netbeans.
I read the "TMate Open Source License" and don't see what's the problem:
Of course INAL and all of that, but it'd be great to hear in more detail why
this is a problem. The ideal solution would be to just include this in Netbeans
out of the box, since it's much more simpler than using external tools and
linking them to the Netbeans SVN support. Writting this again, doesn't make much
sense when there's a product that works very well and seems to have a very
I wrote to TMate and they replied:
TMate Open Source license allows to redistribute SVNKit along with application in case all application source code is
However, sometime ago I was contacted by NetBeans and was said that NetBeans IDE includes closed-source parts (Java
compiler if I recall correctly). In case NetBeans still includes closed-source components (I'm not sure about that and
most probably today NetBeans is completely open sourced) they have to obtain commercial SVNKit license. Same is correct
for closed-source applications built on top of NetBeans platform.
I also read at http://www.javalobby.org/forums/thread.jspa?threadID=97125 that javac is no longer close-sourced. As
such, can the Netbeans team please revisit this issue?
yes it's on our radar for some time and we do plan to revise after NetBeans 6.0.
*** Issue 114832 has been marked as a duplicate of this issue. ***
This would be great! The only let down of current subversion support is the need for the external installation. This
would raise the bar a lot.
We plan to support javahl for 6.5. That should solve couple of problems we have with CLI.
Svnkit is still not an option - we can't ensure that everything built on NetBeans has all code publicly available (open
This is done, for NB 6.5 we support JavaHL from Subversion 1.5. It gets used automatically if you have SVN 1.5
installed. Cmd line is still used if present and JavaHL not available (e.g. for SVN 1.4.x). If not having SVN installed,
an option to automatically download it as a NB plugin from auto update is offered (only for Windows). Should be
available from NB 6.5 beta.