VCS for VSS-Plugin-Sources?
I just noticed that sources for the VSS integration plugin are contained in the dev package.
That's great news to me as I can try and fix the bugs that annoy me most myself.
However it would be easier if I had access to the VCS (subversion or whatever else) for those sources (read-only of course). I could keep track of what I changed and could easily supply a patch.
So is this available somewhere?
Please sign in to leave a comment.
Hello Stephen,
The source for the VSS plugin is currently stored in our internal Perforce
depot, but I think we can move it to the public Subversion repository if
there's interest in that.
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Thanks for the offer.
I think I already did manage to fix the most annoying bug.
Seemed to me that vss integration was completely unable to handle filenames longer than 18 characters.
Please see the code attached to
http://www.jetbrains.net/jira/browse/IDEA-11754
If you could check that and make it into the next EAP version, that would be great!
If it's not too much work I would appreciate if you could move the sources to SVN.
I'll try and fix other bugs as they come along.
Dmitry, a general inquiry:
Do you thinks it is feasible (from a business POV) to extend the vssIntegration plugin to use OLE to integrate with VSS?
I already work on a CommittedChangesProvider so that we get a "Incoming Changes" view in Idea - looking good so far.
One could switch from parsing command line output (yuck) to ole on an as-needed-base.
There's just one snag: I use comfyj to interface with vss.
What do you think: Would it be possible to use that? I noticed you are already using JNIWrapper, so bringing in another companion product might be ok. License isn't too expensive either.
I tried to look at the swt/ole integration that is done in the eclipse vssplugin ... then quickly looked the other way.
In the mid-term comfyj might be interesting for TeamStudio integration, also.
Hello Stephen,
Our experience with using native integration in version control plugins has
been mostly negative so far. We haven't been able to make either the Perforce
native API implementation or ClearCase in native mode to work reliably. Basically,
you get occasional crashes which can't be reliably reproduced and no possibility
to debug or fix them.
It may be the case that VSS with ComfyJ behaves better, but my personal opinion
is that sticking with the command line would be a more supportable solution.
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Those are valid points and I understand your opposition.
OTOH you haven't been able to get VSS integration to work reliably in command line mode either - despite putting lots of effort into it.
Eclipse's vssplugin does indeed use OLE and I haven't experienced or heard of any crashes.
There are simply so many features that are hard to implement and brittle using the command line (getting a file's revision number, detecting files that are deleted in vss, ...).
Of course VSS is near-dead anyway, so let's just turn to more important things.
Dear Stephen,
SF> However it would be easier if I had access to the VCS (subversion or
SF> whatever else) for those sources (read-only of course). I could keep
SF> track of what I changed and could easily supply a patch.
The plugin will be moved to the subversion right after the next EAP on friday.
best wishes,
Michael Gerasimov,
Software Developer
JetBrains, Inc
Hi,
from where can I get these Sources for the VSSIntegration-plugin?
regards
Ok, I found it under http://svn.jetbrains.org/idea/
Thanks