[ANN] TMate plugin version 0.0.36. Early Access Version.

Announcing version 0.0.36 of the TMate plugin, available via the PluginManager or at http://www.tmate.org/eap/

To use the plugin you will need EAP registration code that is available at http://tmate.org/eap/download/ page.

Changes from build 0.0.35 to 0.0.36

  • Plugin: "Pending Updates" tab in TMate tool window displays files that was modified in repository, but not yet updated. Helps to update and resolve conflicts faster.

  • Plugin: Report chart could be displayed as table. User may paste table contents into Excel table or text file.

  • Bugfixes


TMate features overview

- Recognizes and tracks committed CVS transactions
- Allows offline CVS repository browsing in terms of transactions
- Displays files modified in repository but not updated, along with transactions information.
- Tracks CVS repository online and shows transactions that were just commited
- Generates commit statistics as graphic chart or data table
- Supports pserver, ssh1, ssh2 connections

Longer description

TMate plugin adds transactions support to the CVS version control integration. It consists of the server that continuously monitors CVS repository and IDEA plugin that displays found CVS transactions in the IDEA tool window.

TMate Server is implemented as a web application and requires JDK 1.4 and supports CVS repositories accessible through the pserver protocol. TMate Server could be installed locally or on the dedicated computer.

TMate Client is an IDEA plugin that allows to configure remote TMate Server and displays up to date CVS transactions collected by the TMate Server.

TMate IDEA plugin available via the PluginManager includes both TMate Client and TMate Server.

More information about TMate, including screenshots, is available at http://tmate.org/eap/

Your feedback about how the plugin works in your environment, whether do you find it useful, and what features do you want to see in the next versions is very welcome!

Alexander Kitaev.

3 comments

I'm seeing weird stuff in the "pending updates". The nodes of the tree
are file names (full path). When I expand any node I get a single
subnode with a transaction. That transaction contains as subnodes the
sames files as the root nodes. (Does that make sense?)

0

This seems to be correct :) The file name (top level node) is the file that was modified in repository, but not yet updated in your project. The subnode(s) - transactions not updated modifications are included into, and transaction subnodes - files included into this transaction along with the file that needs update.

For instance:
1. In you project you have a file "c:\project\X.java"
2. Another developer modifies this file (and possible some other files) and commits these files.
3. TMate Server detects this transaction (default transaction detection interval is 5 minutes), let's say it called "fix of incorrect update"
4. In the "Pending Updates" tab you have to see the file "c:\project\X.java" (because you need to update it) and below it "fix of incorrect update" transaction. Like this:

-- file: C:\project\X.java, local revision: 1.1 remote revision 1.2
-- transaction: fix of incorrect update
-- /X.java (1.1=>1.2)
-- /Y.java (1.3=>1.4)

5. If there are no possible conflicts (i.e. your local version of "c:\project\X.java" is not modified) you may press "Update" toolbar button in the "Pending Updates" tab and update this very file.
6. If there are possible conflicts (i.e. you have modified your local version of X.java) you have to resolve the conflict before updating the file (use popup menu "Resolve" submenu for possible options).

Do you have any ideas of how to make the "Pending Updates" functionality more clear? May be naming or tree structure needs modifications to make it more understandable?

By the way, may I ask you whether "Go to Source" works with your project now?

Thanks,
Alexander Kitaev.

0

Alexander Kitaev wrote:

This seems to be correct :) The file name (top level node) is the file that was modified in repository, but not yet updated in your project. The subnode(s) - transactions not updated modifications are included into, and transaction subnodes - files included into this transaction along with the file that needs update.


Ok, I understand now. But it definately needed explaining.

One alternate view -- but I'm not saying this is better, I need to play
with the current for a bit first -- would be to make the pending view
similar to the normal transaction centric view, but grey out the files
that are not pending, or have the ability to hide the non-pending files.
One could even imagine merging the two views where files are annotated
with whether they are pending or not. (This could get confusing however
since the grey/non-grey already annotates the read state.) Let me play
for a bit...

By the way, may I ask you whether "Go to Source" works with your project now?


Almost. I can goto all files except those in the 'src/api' directory. If
you recall, those files are in a module which has as its content-root
just a single directory; a directory which is explicitly excluded from
another module. In tihs case the goto file action is disabled, where
before the action would just not function. So tmate clearly knows
something is amiss about these files.

-bk

0

Please sign in to leave a comment.