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 11429] - lcp.bat produces error: "The input line is too long." when directory structure is deep.
Date Wed, 14 Aug 2002 16:53:10 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=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 16:53 -------
I apologize for my hasty reference to java.exe having a file list capability.  
I assumed that since javac supported it, java.exe would too.  

There have been several good suggestions so far.  Patrick's bootstrapping idea 
seems quite reasonable to me -- sounds like there's some code already written 
too.  In fact it sounds like there are some other wins in useability outside of 
this issue, which make it worthwhile on its own.  

Let me expand on a suggestion that Stephanie mentioned.  Modify lcp.bat to 
generate relative classpath pathnames instead of absolute ones.

absolute classpath:

"C:\programs\ant\lib\jar1.jar;C:\programs\ant\lib\jar1.jar;..."

relative classpath:

".\lib\jar1.jar;.\lib\jar1.jar;..."

This is a selfish reccomendation.  It will fix my problem, but perhaps not for 
others in some *really* extreme cases -- It is however, a practical solution, 
and likely an easy modification.

As for the documentation issue.  If you guys want to clearly define the 
directory depth limitation, then I can take that to the JBoss guys and 
say, "Look -- you're putting ant in the wrong place.  The ant docs clearly 
state that ant should be no more than X chars deep in the path."

IMO, their directory structure, although easy to understand, gets too deep.  
They're using ANT like an embedded module instead of as a stand-alone 
application.  I think that's fine, but they should be aware of the 
implications.  

I don't want to take this off-topic, I just want to give some perspective on my 
situation.

As for using the jar manifest to specify the classpath, this IMO is best 
regarded as a last-ditch option, as it makes debugging difficult.  I have 
already had problems with ant-related jars creating a "hidden" classpath 
through the manifest that was undesired.

Thanks again for all the thoughtful comments.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message