Joel,

if you can, don't bother too much with the ant build file - use Maven 
instead. If you'd like a hand with that, feel free to drop me a buzz.

Maven will download and manage all jar files for you amongst other things.
--
dIon Gillard, Multitask Consulting
Work:      http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers


Joel Rees <[EMAIL PROTECTED]> wrote on 10/09/2002 03:01:15 PM:

> Okay, I did the obvious and copied LICENSE from my ANT install into my
> jakarta directory. Now it builds and I have a jar.
> 
> Yay.
> 
> But I have to wonder about build.properties -- there seem to be some
> undocumented assumptions that don't match my directory structure, and I
> don't see anything to tell me not to do it the way I did.
> 
> My directory structure:
> 
> d:\
>   Apache_Group\
>     Apache\
>     jakarta\
>       commons-httpclient\
>       jakarta-ant-1.5\
>       jakarta-log4j-1.2.6\
>       jakarta-oro-2.0.6\
>       LICENSE (copied from ANT)
>     php\
>   ...
>   sun\
>     jdk1.2.1
>     jdk1.3.1_04
>     JRE (1.2 JRE)
>     jsse1.0.3 (the 3 jars copied into each jdk and jre)
> 
> From the HTTPClient build.properties file, it looks as if tomcat is
> expected to be under sun, and as if HTTPClient is expected to be under
> ANT (or maybe Tomcat)?
> 
> Or are things like moving a copy of the LICENSE someplace compatible
> with the build.properties just part of the underlying assumptions?
> 
> (The reason it took me so long to try this is that I get my error
> messages in Japanese and it took me a little bit of thinking to
> recognize that a keikoku during the process of *.html-no seisei for the
> javadoc build really should not prevent the jar from being built, and
> the message about not finding the LICENSE really would be the culprit.
> Okay, so I'm a rank newb.)
> 
> Should I move the HTTPClient subtree down under the ANT subtree? I don't
> plan on installing Tomcat just yet. Or should I just expect to move
> things around a bit as I go?
> 
> > Jeff Dever responded:
> > 
> > > There is no need to modify the classpath.  You should take the 
supplied
> > > build.properties.sample and copy that to build.properties. 
> Modify the properties
> > > to point to the ones you have on your hard disk, whereever they may 
be.
> > 
> > Thanks.
> > 
> > I have already done that, and I'm still getting a failed build. Can't
> > find java.net.URLDecoder or setRequestTimeout, get warnings for those,
> > then build failed, then another warning that it can't find the JAKARTA
> > license to copy.
> > 
> > Probably something not-quite-right in my build.properties.
> > 
> > Hmm. I've commented out the servlet.jar line because I don't have 
Tomcat
> > or anything else in place yet. (Yeah, I'm lazy. Scrubbed my box a 
couple
> > of months back, haven't been doing any server-side Java since then.)
> > I've also got the three Anakia properties lines commented out, since 
I'm
> > not doing anything with xdoc.
> > 
> > I had basically the same set of errors with JUnit in my CLASSPATH as I
> > do with JUnit copied into HTTPClient/lib. (Which makes me wonder if
> > the CLASSPATH would work as well as copying the library.
> > 
> > I'm probably missing something really obvious. Don't have much
> > experience with Java, much less Jakarta, yet.
> > 
> > > Joel Rees wrote:
> > > 
> > > > Okay, I admit I'm not looking very hard, but I didn't find this
> > > > mentioned in the archives with a quick search.
> > > >
> > > > When settup HTTPClient up, should I put JUnit in the CLASSPATH or 
just
> > > > put a copy of the JUnit jar in HTTPClient's lib, like HTTPClient's
> > > > sample build.properties shows?
> > > >
> > > > Feeling like a rank newb, but I'd rather ask than fight error 
messages I
> > > > don't understand yet.
> > 
> 
> -- 
> Joel Rees <[EMAIL PROTECTED]>
> 
> 
> --
> To unsubscribe, e-mail: 
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>
> 


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

Reply via email to