Hi Mark -

Thanks for your added insight.  I too had the suspicion that since ant was
barfing all the time that my classpath was too long, and it is indeed very
long (996 characters).  I'm guessing it probably doesn't need to be that
long, but classpath settings aren't exactly my area of expertise ;)  I
actually store all my JARs in c:\cp\ in an effort to shorten the classpath,
but as you can see, it's still quite long.  Oh well... it looks like Ant
1.6.0 can handle this crazy classpath, but I'll keep this issue in mind for
the future if I get more things barfing at me.

Thanks for all your help everyone,

Matt
----- Original Message ----- 
From: "Mark Norman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 22, 2004 8:00 AM
Subject: RE: [Xdoclet-user] Trouble using hibernate task


Matt,

Your problem was the classpath line was too long. If you look in
ant.bat, you'll see it calls lcp.bat to concatenate all the classpath
locations into one shell variable. There's a maximum length for a
command line so lcp.bat barfed. If you ever want to go back to Ant
1.5.x, try using shorter directory paths for your library locations, or
(assuming you're using Windows) use the SUBST command to provide a drive
letter alias for your library directory. Probably when you switched to
different Java and Ant versions, your directory paths shortened and the
script was able to handle them without exceeding the line length limit.

Cheers
Mark


-----Original Message-----
From: "Sgarlata Matt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Re: [Xdoclet-user] Trouble using hibernate task
Date: Wed, 21 Jan 2004 10:21:21 -0500

Konstantin,

Thanks again for your help; I really appreciate it.

After poking around some more trying to make sure that XDoclet was
gettin=
g
the right java file I realized that Ant was messed up.  Even if I just
ty=
ped
"ant" in a random directory without a build file I got the same error
message:

The input line is too long.
:gotAllArgs
 was unexpected at this time.

I'm not sure what exactly was causing this, but I was able to resolve
the
problem by upgrading to JDK 1.4 and Ant 1.6.0 (I was using JRE 1.3 and
An=
t
1.5.2).

I now have XDoclet working correctly with the example Java class I sent
earlier.

Matt


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to