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=11429>.
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=11429
lcp.bat produces error: "The input line is too long." when directory structure is deep.
------- Additional Comments From mmunz@apelon.com 2002-08-14 13:35 -------
Thanks for taking a look at this.
> What is your suggestion to fix an os limitation ?
At a minimum proper error reporting and documentation. The home directory
string could be checked and an error message along the lines of "Ant must
reside in a directory X characters long or shorter to run properly" issued at
ant startup.
A similar comment should be added in the installation instructions for ant.
By publishing the implicit limitations of a product, you help encourage "design
by contract" -- don't let your application give the impression it can do
something it can't. All operating systems, software, hardware, people,
everything has limitations. For example, Java does not have multiple
inheritance -- this does not prevent one from writing correct programs. A good
user interface manages the limitations of the system so that the user can focus
on their work without distractions. Whether you'd like to think about it or
not, ant.bat has a very real user interface that has a particular defect, as
described in this report.
That having been said, please note that there are two different invocation
methods for ant on w2k -- 1) using ant.bat, or 2) using java invocation (with
the proper classpath, of course)
It is possible to run ant from a "deep" directory using method #2 -- I do it
every day by necessity.
Let me issue a disclaimer:
>> I'm unfamiliar with the details of batch file syntax.
That having been said, it seems to me that the issue here is that lcp.bat
builds up a classpath variable that exceeds the maximum size for the operating
system. As such, I'd imagine that this defect could be replicated in
a "shallow" directory by filling ant's jars directory with many files, or a few
files with long file names.
There are many ways to build up a java classpath. lcp.bat is not the only
one. Perhaps by substituting lcp.bat with another mechanism, you will resolve
this problem.
I'm sorry that I don't have the solution to this problem myself -- I'm just not
a .bat hacker... Thanks again for looking at this issue.
--
To unsubscribe, e-mail: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
|