ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18129] - p4label hangs when setting 'locked' label state w/ JVM 1.3
Date Wed, 19 Mar 2003 18:01:02 GMT
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=18129>.
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=18129

p4label hangs when setting 'locked' label state w/ JVM 1.3





------- Additional Comments From levylambert@tiscali-dsl.de  2003-03-19 18:01 -------
Could you try the patch of P4Label.java which I have attached to be able to run 
your build in verbose mode with JDK 1.3 ? Or would you like me to email you 
an "optional.jar" ?

Maybe the patch could fix your problem. I do not know exactly what is 
happening, but the label spec read with p4 label -o is somewhat corrupted by 
logging. My patch simply does the logging of the label spec after it gets 
copied to a string buffer, rather than before.

The difference in version of Perforce client and server is not a likely 
candidate as a cause of your problem. Perforce does not seem to have stringent 
requirements concerning the matching of client and server. Furthermore, your 
build works fine under JDK 1.2, with the same combination of P4 client and 
server.

This leaves two main suspects : the JDK (bug in JDK 1.3 and 1.4 on Linux ???) 
and ant, specifically P4Label.java and the code of P4Base.java, 
P4HandlerAdapter.java, Execute.java which run Perforce for us.

Mime
View raw message