jakarta-watchdog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramesh Mandava [CONTRACTOR]" <Ramesh.Mand...@eng.sun.com>
Subject Re: PATCH: watchdog-4.0 build and dist directories
Date Wed, 24 Jan 2001 21:26:50 GMT
The initial decision to have build and dist one level above was to use the "ant" 
distribution extracted in the same way. And to go with the way what tomcat is 
doing. As Justy was saying this approach has problems with versioning and won't 
gain us much for watchdog.

  +1 for keeping the build and dist inside the source workspace . 
  
  Thanks
  -Ramesh
  
>Mailing-List: contact watchdog-dev-help@jakarta.apache.org; run by ezmlm
>list-help: <mailto:watchdog-dev-help@jakarta.apache.org>
>list-unsubscribe: <mailto:watchdog-dev-unsubscribe@jakarta.apache.org>
>list-post: <mailto:watchdog-dev@jakarta.apache.org>
>Delivered-To: mailing list watchdog-dev@jakarta.apache.org
>Date: Wed, 24 Jan 2001 13:19:02 -0800
>From: Justyna Horwat <Justyna.Horwat@eng.sun.com>
>X-Accept-Language: en
>MIME-Version: 1.0
>To: watchdog-dev@jakarta.apache.org
>Subject: Re: PATCH: watchdog-4.0 build and dist directories
>Content-Transfer-Encoding: 7bit
>X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N
>
>I was going with the status quo when suggesting the higher level build
>and dist directories. 
>
>I think that the build process would be more well behaved if the project
>did not place files outside of its own directory. Doing this would solve
>several issues including when you have a couple different versions of
>the same workspace each wanting to place files in the identical
>build/dist directory.
>
>+1 on creating the build/dist directories inside the source workspace
>
>Justy
>
>
>"Craig R. McClanahan" wrote:
>> 
>> Justyna Horwat wrote:
>> 
>> > I know some people may be using automated build and testing scripts so
>> > I'm posting to the list first. I would like to create a separate
>> > watchdog-4.0 build and dist directory.
>> >
>> > It would be nice if I knew exactly which watchdog build I was using for
>> > the appropriate version of tomcat.
>> >
>> 
>> I agree with the desire.
>> 
>> As an alternative implementation approach, there seems to be a growing 
sentiment
>> on several of the Jakarta projects to create the "build" and "dist" 
directories
>> *inside* your source directory, rather than "up and over" the way we do it 
now.
>> The change would be as follows:
>> 
>>     -   <property name="watchdog.build" value="../build/watchdog"/>
>>     -   <property name="watchdog.dist" value="../dist/watchdog"/>
>>     +   <property name="watchdog.build" value="build"/>
>>     +   <property name="watchdog.dist" value="dist"/>
>> 
>> What do you think?
>> 
>> >
>> > Justy
>> >
>> 
>> Craig McClanahan
>> 
>> >
>> > Index: build.xml
>> > ===================================================================
>> > RCS file: /home/cvs/jakarta-watchdog-4.0/build.xml,v
>> > retrieving revision 1.7
>> > diff -u -r1.7 build.xml
>> > --- build.xml   2001/01/24 19:53:57     1.7
>> > +++ build.xml   2001/01/24 20:14:21
>> > @@ -3,8 +3,8 @@
>> >     <!-- System property definitions -->
>> >
>> >     <property name="build.compiler" value="classic"/>
>> > -   <property name="watchdog.build" value="../build/watchdog"/>
>> > -   <property name="watchdog.dist" value="../dist/watchdog"/>
>> > +   <property name="watchdog.build" value="../build/watchdog-4.0"/>
>> > +   <property name="watchdog.dist" value="../dist/watchdog-4.0"/>
>> >     <property name="watchdog-classpath"
>> > value="../jakarta-servletapi-4/lib/servlet.jar:./src/tools" />
>> >
>> >     <!-- Prepare the unpacked destination directory -->


Mime
View raw message