ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chappell, Simon P" <Simon.Chapp...@landsend.com>
Subject RE: ANT visions and best practices
Date Thu, 27 Feb 2003 19:06:43 GMT
Good question. I'll try to give a good answer.

My point was that if one of the modules generates what effectively might be thought of as
a library, then when a stable version has been created, copy it across to the other modules
that depend upon it and us it there. We do this internally here, we have a standard corporate
Java library, and when we hit a period of stability, we declare a new version and make it
available to our developers. The periodic release of stable versions allows other developers
to use it while still allowing active development on the library itself. The library is built
with ant and has unit tests, so knowing if we have a stable build is fairly easy).

Concerning naming conventions, I am actually in transition. I used to just label the library
with it's name and no version or datestamp info. So our library was called "landsend.jar".
I am now leaning towards appending version numbers, in the open source style, to the library
name, which would give me something of the order of "landsend-1.2.3.jar" My reason for switching
(to use the Apple term) is that anymore, ant removes the worry of complicated CLASSPATHs anymore.
For many Java tools anymore, just drop a JAR file into a lib directory and "hey presto" it's
available.

Simon

>-----Original Message-----
>From: Andrew Goodnough [mailto:Andrew.Goodnough@wicourts.gov]
>Sent: Thursday, February 27, 2003 12:30 PM
>To: user@ant.apache.org; Chappell, Simon P
>Subject: RE: ANT visions and best practices
>
>
>Just wondering about the comment below - "Use the output from builds as
>the input to other builds".
>
>Do you typically link to the built jars or the loose classes folder of
>other projects?  It might seem picky but I feel a bit safer linking to
>the jar but how do I name the jar dynamically (with datestamp) 
>and still
>be able to link to it from another project during the same build
>process?  Just wondering if there is a common practice...
>
>Andy
>
>
>>>> Simon.Chappell@landsend.com 2/27/2003 11:54:09 AM >>>
>That's quite an application you have there. Looks like this would
>benefit from a divide and conquor approach. Start by figuring out the
>dependencies between deliverables. Can you build the client without the
>DB and EJB's? If you can, then keep that as a sub-project and let it
>have it's own build file. We don't use EJBs here yet, so someone else
>will need to offer code for building those. Build those separately and
>use the resulting JAR files as dependencies for other sub-projects that
>need them.
>
>Summary: build each module as a separate sub-project. Use the output
>from builds as the input to other builds. Keep asking for help.
>
>Pay for overnight shipping on the Ant book or find a bookstore that
>would carry it. Sometimes you just have to bite the bullet and buy the
>book yourself to get the job done in realistic timeframes (just ask my
>poor wife, who shakes her head everytime a parcel arrives from
>Amazon.com at our doorstep!)
>
>Simon
>
>>-----Original Message-----
>>From: Matthias P. [mailto:groups.mpatzak@gmx.de] 
>>Sent: Thursday, February 27, 2003 11:31 AM
>>To: Ant Users List
>>Subject: RE: ANT visions and best practices
>>
>>
>>Hi Simon,
>>
>>it will be a large reporting system (about 20.000.000 EUR in the
>first
>>year). 
>>- Oracle DB
>>- Java Backend with EJBs based on own framework
>>- Websphere Application Server
>>- two logical data storage areas (relational for recording, dwh for
>>reporting)
>>- Java Client based on own framework
>>- (second) Client for Reporting
>>- (bought) Reporting Server
>>- Interfaces to 7 other reporting systems
>>
>>What additional information do u need?
>>
>>Bye, 
>>Matthias
>>
>>
>>> I'll second that. Also, let this list know what manner of 
>>project you 
>>> are building for and perhaps someone here might have a suitable 
>>> build.xml that you can use as a starting point. I know that 
>>I have one 
>>> for building a Struts based WAR file that I could donate to a good 
>>> cause.
>>> 
>>> Simon
>>> 
>>> -----------------------------------------------------------------
>>> Simon P. Chappell                     simon.chappell@landsend.com 
>>> Java Programming Specialist                      www.landsend.com 
>>> Lands' End, Inc.                                   (608) 935-4526
>>> 
>>> 
>>> >-----Original Message-----
>>> >From: Dominique Devienne [mailto:DDevienne@lgc.com] 
>>> >Sent: Thursday, February 27, 2003 11:21 AM
>>> >To: 'Ant Users List'
>>> >Subject: RE: ANT visions and best practices
>>> >
>>> >
>>> >I'd advise to read the Hatcher & Loughran as fast as you can 
>>> >to become an
>>> >Ant expect in no time ;-) --DD
>>> >
>>> >-----Original Message-----
>>> >From: Matthias P. [mailto:groups.mpatzak@gmx.de] 
>>> >Sent: Thursday, February 27, 2003 11:13 AM
>>> >To: user@ant.apache.org 
>>> >Subject: ANT visions and best practices
>>> >
>>> >Hi,
>>> >
>>> >I am new to ANT but need to work with it as the responsible 
>>> >configuration
>>> >manager (Please dont ask why someone who has never worked 
>>with ANT was
>>> >appointed as configuration manager. I hope my manager knows 
>>> >what is best for
>>> >his
>>> >project ;-))
>>> >
>>> >Until now i started to do the tutorials, compile some sources etc.
>
>>> >What i would like to know is what wonders and miracles can be 
>>> >done with ANT?
>>> >
>>> >On what ANT-implementations on your project are you really 
>>proud of? 
>>> >Its just to get an idea and vision what can be done with ANT.
>>> >
>>> >Thank you for your attention. I hope in
> some month i can give 
>>> >you back some
>>> >of my new gained knowledge.
>>> >
>>> >Regards,
>>> >Matthias (from the lovely and sunny Munich)
>>> >
>>> 
>>>---------------------------------------------------------------------
>>> >To unsubscribe, e-mail: user-unsubscribe@ant.apache.org 
>>> >For additional commands, e-mail: user-help@ant.apache.org 
>>> >
>>> >
>>> 
>>>
>---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org 
>>> For additional commands, e-mail: user-help@ant.apache.org 
>>> 
>>
>>-- 
>>+++ GMX - Mail, Messaging & more  http://www.gmx.net +++
>>Bitte l├Ącheln! Fotogalerie online mit GMX ohne eigene Homepage!
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: user-unsubscribe@ant.apache.org 
>>For additional commands, e-mail: user-help@ant.apache.org 
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@ant.apache.org 
>For additional commands, e-mail: user-help@ant.apache.org 
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>For additional commands, e-mail: user-help@ant.apache.org
>
>

Mime
View raw message