Status of MKS Plugin

Hi there,

does anyone know whether the MKS plugin is still being maintained? I hate to stop participating in the Selena EAP, but the plugin has stopped working in build 6700, so I am being forced to go back to build 6667.

Another question (to Jetbrains): Could you imagine adding support for MKS into the core product, so I would get all the goodies like changelists etc.?

Regards,
Jens

8 comments
Comment actions Permalink

I haven't been updating the plug-in because I have moved on to a new employer and I no longer use MKS. Whosoever may be interested in maintaining it is welcome to do so. Attached are the latest files I have.



Attachment(s):
mks.zip
0
Comment actions Permalink

Hi Eric,

thanks for the sources; I'll take a look at them, and if it isn't too complicated, I'll give it a shot.
It looks like I'm stuck in a project with MKS for at least another year, so it would be worth it (unfortunately, all my colleagues use eclipse, and I have a hard time justifying me using IDEA anyway, so if the MKS plugin breaks now, I have one reason less).

Regards,
Jens

0
Comment actions Permalink

Hi,

I had done some modifications to the plugin for private use about one year ago (tried to contact the author, but didn't get any response at that time). Especially adding a tab showing all files that are not up to date in the sandbox (including missing/deleted ones IIRC, thing I never managed to achieve using MKS client)

But, before doing any modifications to the plugin I would advise asking Jetbrains if they believe the OpenAPI for VCS is considered stable for Selena, unless you want to have to modify it again soon.

BTW, wouldn't it be a good idea to put the sources of this plugin in a VCS somewhere ?

0
Comment actions Permalink

Hello Thibaut,

But, before doing any modifications to the plugin I would advise
asking Jetbrains if they believe the OpenAPI for VCS is considered
stable for Selena, unless you want to have to modify it again soon.


Most of the planned changes for Selena are done already - the only planned
major change remaining is modifying DiffProvider and VcsHistoryProvider to
use the new ContentRevision interface instead of the old VcsFileContent.
However, it's likely that we'll have to make a number of smaller changes
which are not planned in advance.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

that's a good news :)

0
Comment actions Permalink



Another question (to Jetbrains): Could you imagine
adding support for MKS into the core product, so I
would get all the goodies like changelists etc.?


Jetbrains, any information on this?

Alternatively, is the OpenAPI open enough (and the relevant sections sufficiently documented) so that this could be added to the MKS plugin?

Regards,
Jens

0
Comment actions Permalink

Hi Eric,

thanks for the sources; I'll take a look at them, and
if it isn't too complicated, I'll give it a shot.


BTW, I did manage to get the plugin to run again, but due to a dire shortage of spare time, I have not done any testing (other than my every-day use which probably does not nearly cover all use cases), so I would prefer to not "release" it at the moment. If anybody is willing to work on it, however, I'll gladly share the sources and binaries.

Regards,
Jens

0
Comment actions Permalink

Hello Jens,

>> Another question (to Jetbrains): Could you imagine adding support for
>> MKS into the core product, so I would get all the goodies like
>> changelists etc.?
>>

Jetbrains, any information on this?


We don't currently have the resources to maintain the MKS plugin internally,
as a bundled version control integration.

Alternatively, is the OpenAPI open enough (and the relevant sections
sufficiently documented) so that this could be added to the MKS
plugin?


Open - yes, documented - not quite. Feel free to ask questions here. :)

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Please sign in to leave a comment.