DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18007>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18007

stcheckin behavior of rootlocalfolder broken

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From [EMAIL PROTECTED]  2003-10-03 20:40 -------
A communication from [EMAIL PROTECTED]
points out a weakness in the documentation about this bug.
"I'm writing this email because I encountered the problem described in
bug 18007, however if the documentation had been a little more explicit,
I think I would not have been able to get my ant build working without
having to find bug 18007.
...
The documentation indicates the following:

'On Windows machines, the mere presence of starteam-sdk.jar on the
classpath is not sufficient for getting these tasks to work properly.
These tasks also require a fully-installed and fully-licensed version of
the StarGate Runtime. This is part of a StarTeam client installation or
may be installed separately. The full client install is not required.'

My computer met this criteria, I had an installed and licensed copy of
the StarGate Runtime, however I was having the same problem. After
reading through the bug 18007, I tripped across a comment about having
the StarGate Runtime .dll files in the executable path, and the
starteam-sdk.jar file be in the classpath. You might want to amend the
documentation to indicate these two conditions."

Since this problem is so annoyingly difficult to deal with, the documentation
should be beefed up to more exactly state the configuration needed.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to