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

Announcing version 0.0.35 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.34 to 0.0.35:

  • Server: built-in SSH support (public/private key authorization is supported for SSH2 and password authorization for SSH1)

  • Plugin: ability to generate graphical reports for the set of transactions using various criterias

  • Bugfixes


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.

24 comments

Hura, hura, hura. SSH support.
Thx Alex.

Best regards,
Rafal

U¿ytkownik "Alexander Kitaev" <no_mail@jetbrains.com> napisa³ w wiadomo¶ci
news:26638968.1077996418026.JavaMail.javamailuser@localhost...

Announcing version 0.0.35 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.34 to 0.0.35:

>

  • * Server: built-in SSH support (public/private key authorization is

supported for SSH2 and password authorization for SSH1)

  • * Plugin: ability to generate graphical reports for the set of

transactions using various criterias

  • * Bugfixes

>

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.



0

Hello Alexander,

Thanks for ssh support! It makes a world of difference.
However I also have to report some serious refresh issues in the server configuration panel.
Case1:
1. Add a new component and a module in it.
2. Upload config to server.
3. Close the server config.
4. Reopen it.
=> The added component & module are gone.
Case2:
1. Delete component.
2. Upload config to server
3. Close and reopen server config
=> component still here

This had me run in a loop for a while until I saw that I got modifications from modules that I just created. So the server is correctly updated but somehow the plugin is out-of-sync.

Hope this helps

Using IDEA 1172

Jacques

0

Hello Jacques,

JM> Using IDEA 1172
I mena 1171 obviously. Got messed up with OmniaMea 142... ;)


0

Looks very good. However, we have some people not using IntelliJ. Are any
other clients available?
A servlet/jsp interface would be great. Is the protocol public - in that
case we might be able to do one ourselves?





0

Hello Jacques,

Unfortunately, this is expected behaviour, rather then a bug. TMate Server configuration modification consists of the following steps:

1. Client downloads current configuration and opens "Edit configuration" dialog.
2. User modifies configuration and uploads it to TMate Server.
3. Server puts "update configuration" requests into the requests queue (FIFO queue).
4. Server process "update configuration" requests as soon as all the pending requests are processed. Processing configuration request may take a while, because TMate Server automatically reindexes transactions for new and modified components.
5. Server makes updated configuration available to the clients.

So, if one modifies configuration and tries to modify it again, the "old" configuration will be downloaded to the client, untill the steps 3-5 are processed by the server.

I will think about how to avoid the situation you've described. I suppose that there should be at least a warning dialog that says that there is configuration that is not processed by the server yet or server should provide "last uploaded" configuration for editing, not the "current" one.

Thanks,
Alxander Kitaev.

0

Now I can open some files, but not others. I no longer see the double
port in the log.

I'm guessing the problem lies in that my idea modules do not mirror my
cvs modules. The one file I have been able to open has an idea module
that has the same name as the cvs module and has as its content root the
cvs module.

-bk

-



[F.A:541] building local modules for: deployment
[F.A:554] processing content root:
C:/cvs.local/its.dev/infrastructure
[F.A:554] processing content root:
C:/cvs.local/its.dev/deployment
[F.A:554] processing content root:
C:/cvs.local/its.dev/clients/webtrader
[F.A:554] processing content root:
C:/cvs.local/its.dev/trading/src/api
[F.A:554] processing content root:
C:/cvs.local/its.dev/clients/webadmin
[F.A:554] processing content root: C:/cvs.local/its.dev
[F.A:554] processing content root:
C:/cvs.local/its.dev/clients/webclient
[F.A:554] processing content root:
C:/cvs.local/its.dev/clients/webcommon
[F.A:554] processing content root:
C:/cvs.local/its.dev/thirdparty
[F.A:561] revisions found: 9
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/infrastructure
[D.A:35] creating local module for:
C:/cvs.local/its.dev/infrastructure, deployment
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: infrastructure
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/deployment
[D.A:47] Remote Module Name: deployment
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/deployment
[D.A:35] creating local module for:
C:/cvs.local/its.dev/deployment, deployment
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: deployment
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/deployment
[D.A:47] Remote Module Name: deployment
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:58] Local matches exactly
[F.A:568] local module is created
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/clients/webtrader
[D.A:35] creating local module for:
C:/cvs.local/its.dev/clients/webtrader, deployment
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: clients/webtrader
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/deployment
[D.A:47] Remote Module Name: deployment
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/trading/src/api
[D.A:35] creating local module for:
C:/cvs.local/its.dev/trading/src/api, deployment
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: trading/src/api
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/deployment
[D.A:47] Remote Module Name: deployment
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/clients/webadmin
[D.A:35] creating local module for:
C:/cvs.local/its.dev/clients/webadmin, deployment
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: clients/webadmin
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/deployment
[D.A:47] Remote Module Name: deployment
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root: C:/cvs.local/its.dev
[D.A:35] creating local module for: C:/cvs.local/its.dev,
deployment
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: all
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/deployment
[D.A:47] Remote Module Name: deployment
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/clients/webclient
[D.A:35] creating local module for:
C:/cvs.local/its.dev/clients/webclient, deployment
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: clients/webclient
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/deployment
[D.A:47] Remote Module Name: deployment
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/clients/webcommon
[D.A:35] creating local module for:
C:/cvs.local/its.dev/clients/webcommon, deployment
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: clients/webcommon
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/deployment
[D.A:47] Remote Module Name: deployment
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/thirdparty
[D.A:35] creating local module for:
C:/cvs.local/its.dev/thirdparty, deployment
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: thirdparty
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/deployment
[D.A:47] Remote Module Name: deployment
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:574] totally 1 local modules was created
[S.B:834] local module : deployment
[F.A:494] looking in 1 local modules
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[F.A:498] resolved local path:
C:/cvs.local/its.dev/deployment/common/conf/properties/exchange-dev.properties
[F.A:503] resolved 1 paths
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[D.E:97] resolving:
common/conf/properties/exchange-dev.properties
[F.A:541] building local modules for: trading
[F.A:554] processing content root:
C:/cvs.local/its.dev/infrastructure
[F.A:554] processing content root:
C:/cvs.local/its.dev/deployment
[F.A:554] processing content root:
C:/cvs.local/its.dev/clients/webtrader
[F.A:554] processing content root:
C:/cvs.local/its.dev/trading/src/api
[F.A:554] processing content root:
C:/cvs.local/its.dev/clients/webadmin
[F.A:554] processing content root: C:/cvs.local/its.dev
[F.A:554] processing content root:
C:/cvs.local/its.dev/clients/webclient
[F.A:554] processing content root:
C:/cvs.local/its.dev/clients/webcommon
[F.A:554] processing content root:
C:/cvs.local/its.dev/thirdparty
[F.A:561] revisions found: 9
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/infrastructure
[D.A:35] creating local module for:
C:/cvs.local/its.dev/infrastructure, trading
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: infrastructure
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/trading
[D.A:47] Remote Module Name: trading
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/deployment
[D.A:35] creating local module for:
C:/cvs.local/its.dev/deployment, trading
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: deployment
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/trading
[D.A:47] Remote Module Name: trading
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/clients/webtrader
[D.A:35] creating local module for:
C:/cvs.local/its.dev/clients/webtrader, trading
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: clients/webtrader
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/trading
[D.A:47] Remote Module Name: trading
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/trading/src/api
[D.A:35] creating local module for:
C:/cvs.local/its.dev/trading/src/api, trading
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: trading/src/api
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/trading
[D.A:47] Remote Module Name: trading
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:60] Local is above remote
[F.A:568] local module is created
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/clients/webadmin
[D.A:35] creating local module for:
C:/cvs.local/its.dev/clients/webadmin, trading
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: clients/webadmin
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/trading
[D.A:47] Remote Module Name: trading
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root: C:/cvs.local/its.dev
[D.A:35] creating local module for: C:/cvs.local/its.dev,
trading
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: all
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/trading
[D.A:47] Remote Module Name: trading
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/clients/webclient
[D.A:35] creating local module for:
C:/cvs.local/its.dev/clients/webclient, trading
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: clients/webclient
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/trading
[D.A:47] Remote Module Name: trading
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/clients/webcommon
[D.A:35] creating local module for:
C:/cvs.local/its.dev/clients/webcommon, trading
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: clients/webcommon
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/trading
[D.A:47] Remote Module Name: trading
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:565] processing local CVS root:
C:/cvs.local/its.dev/thirdparty
[D.A:35] creating local module for:
C:/cvs.local/its.dev/thirdparty, trading
[D.A:40] Local CVS Root: :pserver:host:2401:/cvs/its
[D.A:41] Local Module Name: thirdparty
[D.A:42] Local Branch: HEAD
[D.A:45] Remote CVS Root: :pserver:host:2401:/cvs/its/trading
[D.A:47] Remote Module Name: trading
[D.A:49] Converted remote CVS Root: :pserver:host:2401:/cvs/its
[D.A:66] Local module will not be created
[F.A:571] can't create local module
[F.A:574] totally 1 local modules was created
[S.B:834] local module : trading
[F.A:494] looking in 1 local modules
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[F.A:498] resolved local path: null
[F.A:503] resolved 0 paths
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve
[D.E:97] resolving:
src/impl/com/its/marketdata/service/bar/AbstractBarManager.java
[D.E:116] can't resolve

0

I am attempting to alter my server module definitions. I define a new
component, then add the cvs modules. Then I add another
component, but now the select cvs module dialog hangs after selecting
the cvs server and clicking next. Seems I have to shutdown idea for each
time I want to add new cvs module.

I remember a problem like this in the past. Dont' know if this is the
same or similar.

0

As part of redoing my tmate config [to try and find a combination in
which files can be opened in idea] I have completely screwed something
up. Now I see the messages that the server is reindexing and such, my
filters show all my components and modules, but I get nothing within
idea. Also, the log file is empty.

Hmm, well this is a pretty useless report, I know. But I don't know what
else to do. I've restarted the server, restarted idea, rebuild all all
the tmate configs.


Barry Kaplan wrote:

I am attempting to alter my server module definitions. I define a new
component, then add the cvs modules. Then I add another
component, but now the select cvs module dialog hangs after selecting
the cvs server and clicking next. Seems I have to shutdown idea for each
time I want to add new cvs module.

I remember a problem like this in the past. Dont' know if this is the
same or similar.


--
Barry Kaplan
Integrated Trading Solutions
bkaplan@integratedtrading.com

0

Hello Alexander,

AK> Hello Jacques,
AK>
AK> Unfortunately, this is expected behaviour, rather then a bug. TMate
AK> Server configuration modification consists of the following steps:
AK>
AK> 1. Client downloads current configuration and opens "Edit
AK> configuration" dialog.
AK>
AK> 2. User modifies configuration and uploads it to TMate Server.
AK>
AK> 3. Server puts "update configuration" requests into the requests
AK> queue (FIFO queue).
AK>
AK> 4. Server process "update configuration" requests as soon as all the
AK> pending requests are processed. Processing configuration request may
AK> take a while, because TMate Server automatically reindexes
AK> transactions for new and modified components.
AK>
AK> 5. Server makes updated configuration available to the clients.
AK>
AK> So, if one modifies configuration and tries to modify it again, the
AK> "old" configuration will be downloaded to the client, untill the
AK> steps 3-5 are processed by the server.
AK>
AK> I will think about how to avoid the situation you've described. I
AK> suppose that there should be at least a warning dialog that says
AK> that there is configuration that is not processed by the server yet
AK> or server should provide "last uploaded" configuration for editing,
AK> not the "current" one.
AK>
AK> Thanks,
AK> Alxander Kitaev.
Here are some ideas that you might find helpful. I ordered them in what I believe is increasing order of effort:
1. On configuration panel open, parse the request queue for configuration modification and disable editing if there are pending requests and display "Request pending" message.
2. 1. + cancel pending requests button that would cancel all requests except configuration updates
3. Cache configuration updates to client. Since I haven't used the server edition I don't know how you resolve multi-client updates. It might not be feasible because of that.
4. Copy configuration when serving cvs update requests. The modifiable configuration is always available to be updated.

In addition I think you should re-validate pending requests based on the new configuration: the user might have removed modules so you don't want to fetch their information anymore... filters could have been changed...

BTW how do you manage multi-user configuration updates today? The last user wins? Maybe you should switch to pessimistic locking.

Jacques


0

Hello Jacques,

Thank you for your suggestions! As a final solution I think I will implement it the following way:

1. Configuration Editor will always edit the last uploaded configuration, not the "active" one. When user uploads configuration it becomes "edtiable" even if it was not processed by the server yet.

2. TMate Server should support requests coalescing to make sure it will not perform unnecessary indexing or update when there is a configuration update request pending, i.e. putting configuration request into the queue should discard all (or some of) the pending events in the queue and apply as soon as possible.

3. Make client to display warning messages when there was a configuration update by the other user during configuration editing.

I suppose that described approach will solve most of the problems and will make configuration editing process more logical from the user's point of view. I think "locking" configuration for editing also makes sense but requires more efforts to implement and thus it is relatively seldom operation usually performed by one "admin" user, it doesn't worth the efforts.

Thanks,
Alexander Kitaev.

0

Hello Niels,

There are plans to provide clients for other IDEs and rich web client, but only after the first release (planned for the end of March).

If you're interested in implementing simple web client existing protocol could fit your needs. The protocol is not fixed and may be changed at any time, however I suppose that it will not be changed significantly till the first release.

Protocol specification is available at http://tmate.org/eap/specs/

Alexander Kitaev.

0

Hello,

Recently I've submitted an SCR to the IDEA tracker and this bug is marked as "fixed" in 4.0. (see http://www.intellij.net/tracker/idea/viewSCR?publicId=29176 for details). As far as I remember Jacques Morel reported that resizing "Select Module" dialog may solve the problem, another workaround is restarting IDEA.

What build of IDEA you're using? May be this problem was fixed in 4.0, but reappeared in the EAP builds that were built after 4.0. release. I'm working with the build #1162 and didn't manage to reproduce this bug. Anyway, if this problem will persist, I will provide my own "Select Module" dialog to avoid the deadlock.

Thanks for pointing to the problem!
Alexander Kitaev.

0

Hello,

First I would like to say that you're probably the best EAP user one could wish to get :) Thank you for reporting all the problems you have with TMate and not giving up!

To restore TMate I may suggest you to try the following:

1. Create another connection to the running TMate Server in IDEA (use TMate | Manage Connections menu). This will make plugin to reload all the information from the TMate Server and will create new set of TMate Plugin configuration files. If you would like to recreate connection with the same name as before, first delete connections, close the "Manage Connections" dialog, open it again and create new connections.

2. If the above will not help, reinstall TMate Server completely and recreate the connection in the plugin as described above. Please note, that TMate plugin 0.0.35 requires TMate Server 0.0.35 as well to work correctly.

Thanks,
Alexander Kitaev.

0

Hello,

Thank you for posting the log file. Accordingly to this log file TMate plugin discovered the following while trying to locate project file that matches to the repository file src/impl/com/its/marketdata/service/bar/AbstractBarManager.java (located in repository :pserver:host:2401:/cvs/its, module trading) :

1. It located 9 cvs root folders in your project. Among these roots it located one matching root that refers to the same repository and module as the source file it would like to open: :pserver:host:2401:/cvs/its, module: trading/src/api

2. It converted the local cvs root description, making assumption that it contains files below src/api folder in module trading in repository :pserver:host:2401:/cvs/its

3. When looking for the file in this local root it discovered that repository file is located below src/impl, not src/api and failed to find the project file in this root.

Could you please write what step of the above steps was incorrect, i.e. whether there are other local cvs roots that contain this very file (step 1) or whether the local root that was found may contain not only files that are below src/api folder (step 2 and 3)?

Thanks a lot in advance!
Alexander Kitaev.

0

I'm using 1165.

Alexander Kitaev wrote:

Hello,

Recently I've submitted an SCR to the IDEA tracker and this bug is marked as "fixed" in 4.0. (see http://www.intellij.net/tracker/idea/viewSCR?publicId=29176 for details). As far as I remember Jacques Morel reported that resizing "Select Module" dialog may solve the problem, another workaround is restarting IDEA.

What build of IDEA you're using? May be this problem was fixed in 4.0, but reappeared in the EAP builds that were built after 4.0. release. I'm working with the build #1162 and didn't manage to reproduce this bug. Anyway, if this problem will persist, I will provide my own "Select Module" dialog to avoid the deadlock.

Thanks for pointing to the problem!
Alexander Kitaev.


--
Barry Kaplan
Integrated Trading Solutions
bkaplan@integratedtrading.com

0

Well, this is pretty much what I did. I deleted the connection, closed
idea, recreated the connection, defined components, added modules (then
restarted idea and repeated for each module because of the previous
issue). I also updated the server war when I first updated to .35. But
I'll give it another go today, and make sure all the tomcat work
directories are cleared.


Alexander Kitaev wrote:

Hello,

First I would like to say that you're probably the best EAP user one could wish to get :) Thank you for reporting all the problems you have with TMate and not giving up!

To restore TMate I may suggest you to try the following:

1. Create another connection to the running TMate Server in IDEA (use TMate | Manage Connections menu). This will make plugin to reload all the information from the TMate Server and will create new set of TMate Plugin configuration files. If you would like to recreate connection with the same name as before, first delete connections, close the "Manage Connections" dialog, open it again and create new connections.

2. If the above will not help, reinstall TMate Server completely and recreate the connection in the plugin as described above. Please note, that TMate plugin 0.0.35 requires TMate Server 0.0.35 as well to work correctly.

Thanks,
Alexander Kitaev.


--
Barry Kaplan
Integrated Trading Solutions
bkaplan@integratedtrading.com

0

The file in question is physically located under 'trading/src/impl', no
'trading/src/api'. I think the problem has to do with idea module
limitations relating to not sharing context roots. Here's what I have:

- module 'server-remote' with a context root of 'trading/src/api'
- module 'server' with a context root of 'trading' with
'trading/src/api' excluded (under the 'trading' context root is the
directory 'trading/src/impl')

I have this crazy setup because the 'trading/src/api' is depended on by
various clients of our servers and we want enforce that the clients
don't depend on any non-remotable interface. A better cvs stuctured
would be to have the remote api classes in a cvs module like
'trading-remote' or some such. But that would cause a bit a headache
with CVS. (...dreaming of full subversion integration in idea...).

---

On a related topic, I'm a bit confused as to the motivation of tmate
components? Why not map cvs modules directly under the connection?



Alexander Kitaev wrote:

Hello,

Thank you for posting the log file. Accordingly to this log file TMate plugin discovered the following while trying to locate project file that matches to the repository file src/impl/com/its/marketdata/service/bar/AbstractBarManager.java (located in repository :pserver:host:2401:/cvs/its, module trading) :

1. It located 9 cvs root folders in your project. Among these roots it located one matching root that refers to the same repository and module as the source file it would like to open: :pserver:host:2401:/cvs/its, module: trading/src/api

2. It converted the local cvs root description, making assumption that it contains files below src/api folder in module trading in repository :pserver:host:2401:/cvs/its

3. When looking for the file in this local root it discovered that repository file is located below src/impl, not src/api and failed to find the project file in this root.

Could you please write what step of the above steps was incorrect, i.e. whether there are other local cvs roots that contain this very file (step 1) or whether the local root that was found may contain not only files that are below src/api folder (step 2 and 3)?

Thanks a lot in advance!
Alexander Kitaev.


--
Barry Kaplan
Integrated Trading Solutions
bkaplan@integratedtrading.com

0

Aha, seems that I understand now.

I think long explanations with my english will be a bit confusing :) so may you please answer if the following is correct:

1. your project contains module with content root "C:/cvs.local/its.dev". This root contains "src/impl" folder that is not "excluded".
2. file "C:/cvs.local/its.dev/CVS/Repository" contains string "all" (TMate will probably work correctly if there will be an empty string in this file).

If the above is correct, it is interesting how did you checked out files to this folder. Did you use certain CVS client or IDEA itself to checkout modules or did you use cvs module aliases?

Thanks a lot for your help in solving the problem!
Alexander Kitaev.

0

Component mainly serves to logically group the modules and as a base to form the transactions information (one may refer to different components as to different TMate servers).

For example on my previous job, we had a big project with several repositories for different parts of the project and several teams working with the project as with a set of more or less independent components (every component contained several modules, actulally a lot of modules - it was an Eclipse project). Also, there were several "utility" projects not related to the main project. I suppose that all these components fits TMate "components" model quite well, and probably most of the large projects will gain some benefits with such model. Of course there is a possibility to install as many TMate servers as needed, but in some cases centralized configuration is better.

Alexander Kitaev.

0


Alexander Kitaev wrote:

1. your project contains module with content root "C:/cvs.local/its.dev". This root contains "src/impl" folder that is not "excluded".


Yes, the 'server' module has a context of root of "C:/cvs.local/its.dev"
where "src/impl" is /not/ excluded. Actually this directory is at
"trading/src/impl" under the content root.

The 'server' module is kinda strange in that I need to include the ant
scripts stored directly under "C:/cvs.local/its.dev", so the 'server'
module, which would normally have a content root of
"C:/cvs.local/its.dev/trading" (ie, trading is another name for server
in our system) must have "C:/cvs.local/its.dev". It then exludes a bunch
of other directories that so that can be the content roots of other modules.

For example, the 'server-remote' module (the which contained the file I
could not open via tmate) has a content root of
"C:/cvs.local/its.dev/tradng/src/api" with its sole source directory
being ".". This module exists just to enforce the one-way dependency
from server,clients->server-remote.

2. file "C:/cvs.local/its.dev/CVS/Repository" contains string "all" (TMate will probably work correctly if there will be an empty string in this file).


Yes, 'all' is a module alias that we use to checkout. Generally its
checked out using smartcvs. Idea and smartcvs are used interchangably
throughout development.

The definition of 'all' is:

all all &clients &trading &infrastructure &thirdparty &deployment

When I checkout the 'all' module/alias I indicate to cvs to place it in
a directory of a different name. In the examples above, that was
"C:/cvs.local/its.dev".

Generally I have several instances of the repository on local disk (eg,
one for development, one of the trunk so I if I screw up my development
checkout I can run tests which will pass, one for the eap branch, one
for the production branch).

Thanks a lot for your help in solving the problem!


A pleasure, I assure you. And well worth it also Alexander; tmate is
fantastic.

--
Barry Kaplan
Integrated Trading Solutions
bkaplan@integratedtrading.com

0

Hello, i have exception on update changes:
a.. 04.03.2004, 14:21:51: org.tmatesoft.tmate.server.vcs.VCSException:
Cannot convert character 41d at
org.tmatesoft.tmate.server.vcs.ccvs.CVSSupportRO.diff(Unknown Source) at
org.tmatesoft.tmate.server.C.B.A(Unknown Source) at
org.tmatesoft.tmate.server.C.F.A(Unknown Source) at
org.tmatesoft.tmate.server.C.C.run(Unknown Source) Caused by:
org.tmatesoft.tmate.server.vcs.VCSException: Cannot convert character 41d at
org.tmatesoft.tmate.server.vcs.ccvs.E.rlog(Unknown Source) at
org.tmatesoft.tmate.server.vcs.ccvs.CVSSupportRO$3.A(Unknown Source) at
org.tmatesoft.tmate.server.vcs.ccvs.G.A(Unknown Source) ... 4 more Caused
by: org.A.A.A.I.E: Cannot convert character 41d at org.A.A.A.I.B.A(Unknown
Source) at org.A.A.A.I.D.write(Unknown Source) at
java.io.Writer.write(Writer.java:150) at
java.io.Writer.write(Writer.java:126) at org.A.A.A.F.A(Unknown Source) at
org.A.A.A.F.B(Unknown Source) at org.A.A.A.F.A(Unknown Source) at
org.A.A.A.F.A(Unknown Source) at
org.tmatesoft.tmate.server.vcs.ccvs.E.processRequests(Unknown Source) ... 7
more


0

Ok, I'm back up running again. I did what I said below. (Still have the
open problems though.)


Barry Kaplan wrote:

Well, this is pretty much what I did. I deleted the connection, closed
idea, recreated the connection, defined components, added modules (then
restarted idea and repeated for each module because of the previous
issue). I also updated the server war when I first updated to .35. But
I'll give it another go today, and make sure all the tomcat work
directories are cleared.


Alexander Kitaev wrote:

>> Hello,
>>
>> First I would like to say that you're probably the best EAP user one
>> could wish to get :) Thank you for reporting all the problems you have
>> with TMate and not giving up!
>>
>> To restore TMate I may suggest you to try the following:
>>
>> 1. Create another connection to the running TMate Server in IDEA (use
>> TMate | Manage Connections menu). This will make plugin to reload all
>> the information from the TMate Server and will create new set of TMate
>> Plugin configuration files. If you would like to recreate connection
>> with the same name as before, first delete connections, close the
>> "Manage Connections" dialog, open it again and create new connections.
>>
>> 2. If the above will not help, reinstall TMate Server completely and
>> recreate the connection in the plugin as described above. Please note,
>> that TMate plugin 0.0.35 requires TMate Server 0.0.35 as well to work
>> correctly.
>> Thanks,
>> Alexander Kitaev.



--
Barry Kaplan
Integrated Trading Solutions
bkaplan@integratedtrading.com

0

Hello Alexey,

Thank you for posting the report! I think it will be fixed in the next TMate build.

The reason of exception is that request that was sent to the CVS server contained non-ascii character, that CVS server may not process correctly and CVS library throws an exception on attempt to send such request. TMate server first reads the CVS server ouptut, converting it into unicode strings (using server system encoding by default) and then may use converted information to send back to the CVS server (however not converting them back into single character encoding, and it works fine only for latin1 chars - that what I'm going to fix). May I ask you whether my assumptions are correct? In other words - do you have filenames in CVS that includes not only latin1 characters?

Thanks,
Alexander Kitaev.

0

Thank you for the detailed explanations, now it is more or less clear that the reason of the opening problem is using of the "ampersand" CVS module alias.

Version of TMate plugin you're using can't detect that "all" module is actually corresponds to the CVS repository root and fails to locate project files below the folder that corresponds to the aliased module ("all" in your case).

To check this you may temporary replace "all" with empty string in the "c:/cvs.local/its.dev/CVS/Repository" file and I suppose that TMate will be able to open files. Fix for this problem (support for "ampersand" CVS module aliases) will be included into the next build.

Thank you!
Alexander Kitaev.

0

Please sign in to leave a comment.