You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Howard Lee <ho...@earthlink.net> on 2000/12/02 16:53:36 UTC

Could you please?

Could any of you please send me a basic build.xml file? I'm new to Ant, and
am having a tough time getting it to compile when I add classpath in it.
Thank you very much.

howard


RE: Could you please?

Posted by Chris Todd <ch...@christophertodd.com>.
>-----Original Message-----
>From: Peter Donald [mailto:donaldp@apache.org]
>Sent: Saturday, December 02, 2000 4:19 PM
>To: ant-user@jakarta.apache.org
>Subject: RE: Could you please?
>
>
>At 03:01  2/12/00 -0500, you wrote:
>>This request makes me wonder whether it might be worth it to create some
>>sort of build file 'repository' or 'library' (in the public library sense,
>>rather than the programming sense).  While the Ant docs are really good
>>(IMHO), particularly for an open source project, it sometimes
>helps newbies
>>to see examples of entire build files.
>
>I agree. It also promotes a good directory structure layout ;)

I certainly found that to be the case.

>I started a
>standards type document a while back as a sort of best practices build
>description. It included things like names of targets, directory structure
>etc. I guess it would be good to dust that off and see what
>everyone thinks ;)

I would certainly be interested in it.  After I sent my email, though, I
wondered if I had opened a can of worms, since we may find that everyone has
their own opinion of what constitutes "best practices"!  :-)

>
>>As I work more and more with Ant, I am beginning to see
>build-related design
>>patterns.  Perhaps we could somewhow catalog those Ant-related
>>design/usage/style patterns?  Just a thought.
>
>Very good thought ;)
>
>Cheers,
>
>Pete
>
>*-----------------------------------------------------*
>| "Faced with the choice between changing one's mind, |
>| and proving that there is no need to do so - almost |
>| everyone gets busy on the proof."                   |
>|              - John Kenneth Galbraith               |
>*-----------------------------------------------------*

Sincerest regards,
Chris Todd
Software Engineer
Alabanza Corporation


RE: Could you please?

Posted by Peter Donald <do...@apache.org>.
At 03:01  2/12/00 -0500, you wrote:
>This request makes me wonder whether it might be worth it to create some
>sort of build file 'repository' or 'library' (in the public library sense,
>rather than the programming sense).  While the Ant docs are really good
>(IMHO), particularly for an open source project, it sometimes helps newbies
>to see examples of entire build files.

I agree. It also promotes a good directory structure layout ;) I started a
standards type document a while back as a sort of best practices build
description. It included things like names of targets, directory structure
etc. I guess it would be good to dust that off and see what everyone thinks ;)

>As I work more and more with Ant, I am beginning to see build-related design
>patterns.  Perhaps we could somewhow catalog those Ant-related
>design/usage/style patterns?  Just a thought.

Very good thought ;)

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*


RE: Could you please?

Posted by Erik Meade <em...@geekfarm.org>.
> -----Original Message-----
> From: Chris Todd
>
> As I work more and more with Ant, I am beginning to see 
> build-related design
> patterns.  Perhaps we could somehow catalog those Ant-related
> design/usage/style patterns?  Just a thought.
> 
> Sincerest regards,
> Chris Todd
> Software Engineer
> Alabanza Corporation

I think this is a good line to run down, just last night while trying
to setup JBuilder to run Ant's and JUnit's Open Tools.  I was thinking
how nice it would be if there was a standardized project setup like
ports in FreeBSD.  I wonder if this gets close to JPAN
(http://marc.theaimsgroup.com/?l=ant-dev&m=97511570926663&w=2)?

--
Erik Meade             emeade@objectmentor.com
Senior Consultant      Object Mentor, Inc.
http://www.junit.org
 



RE: Could you please?

Posted by Chris Todd <ch...@christophertodd.com>.
This request makes me wonder whether it might be worth it to create some
sort of build file 'repository' or 'library' (in the public library sense,
rather than the programming sense).  While the Ant docs are really good
(IMHO), particularly for an open source project, it sometimes helps newbies
to see examples of entire build files.

I still consider myself an Ant newbie, and I've learned a lot from reading
other peoples' build files, particularly other OSS projects (e.g. JDOM,
Castor, Ant, Tomcat, practically any java-related apache project, etc.).
Seeing how an entire build file is put together is something that is hard to
get from the docs, which present each task on its own and independent of all
other tasks.  Not only am I an Ant newbie, but also a general
Java/programming newbie, and I've learned a lot about how to organize a
software project from examining build files (the 'Developing Web
Applications with Tomcat' doc that comes with Tomcat was also good in that
regard).

As I work more and more with Ant, I am beginning to see build-related design
patterns.  Perhaps we could somewhow catalog those Ant-related
design/usage/style patterns?  Just a thought.

Sincerest regards,
Chris Todd
Software Engineer
Alabanza Corporation

>-----Original Message-----
>From: Michael O. Duffy [mailto:mduffy01@snet.net]
>Sent: Saturday, December 02, 2000 2:53 PM
>To: ant-user@jakarta.apache.org
>Subject: Re: Could you please?
>
>
>
>Howard:
>
>Here's a generic one that I use for projects.  It assumes a
>standard directory
>structure (src for .java files, classes for .class files, lib for
>.jar files,
>docs for javadocs, etc.).  There are five useful tasks:
>
>clean - flushes out the classes directory and the .jar files.
>compile - compiles all the .java source files.
>deploy - creates a .jar file and puts it in the deploy directory.
>test - runs JUnit tests
>docs - generates javadocs
>
>I can reuse it for other projects just by changing a few
>parameters.  I hope
>you like it, too.
>
>If anybody has any suggestions or improvements, please let me
>know.  Thanks -
>MOD
>
>
>Howard Lee wrote:
>
>> Could any of you please send me a basic build.xml file? I'm new
>to Ant, and
>> am having a tough time getting it to compile when I add classpath in it.
>> Thank you very much.
>>
>> howard
>


Re: Could you please?

Posted by "Michael O. Duffy" <md...@snet.net>.
Howard:

Here's a generic one that I use for projects.  It assumes a standard directory
structure (src for .java files, classes for .class files, lib for .jar files,
docs for javadocs, etc.).  There are five useful tasks:

clean - flushes out the classes directory and the .jar files.
compile - compiles all the .java source files.
deploy - creates a .jar file and puts it in the deploy directory.
test - runs JUnit tests
docs - generates javadocs

I can reuse it for other projects just by changing a few parameters.  I hope
you like it, too.

If anybody has any suggestions or improvements, please let me know.  Thanks -
MOD


Howard Lee wrote:

> Could any of you please send me a basic build.xml file? I'm new to Ant, and
> am having a tough time getting it to compile when I add classpath in it.
> Thank you very much.
>
> howard