You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Paul Hammant <Pa...@yahoo.com> on 2002/03/29 10:40:45 UTC

ant.properties

Folks,

I am finding it difficult to complete the setup necessary to build 
excalibur from scratch.  And I am not a newbie.

Given that ant.properties is reuired in a number of places (or at least 
the properties they define are), I though the following may be useful if 
added to pertinent places of the build files :

Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/all/build.xml,v
retrieving revision 1.118
diff -r1.118 build.xml
195c195,199
<   <target name="check-datasource" depends="check-environment" 
if="datasource.present">
---
 >   <target name="check-ant-properties" 
unless="excalibur-collections.home">
 >      <fail message="You need an ant.properties to build excalibur.  
Either one in your home dir, or one the jakarta-avalon-excalibur/all 
dir. There is an ant.properties.sample that can be copied for this need."/>
 >   </target>
 >
 >   <target name="check-datasource" depends="check-environment, 
check-ant-properties" if="datasource.present">

Note that it is checking for a single property from each build file and 
not the presence of the local build file...

Thoughts?

- Paul


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: ant.properties

Posted by Paul Hammant <Pa...@yahoo.com>.
Peter,

>On Fri, 29 Mar 2002 21:55, Paul Hammant wrote:
>
>>We will have gone from a position of an easy build of a big jar (that
>>itself being an acceptance problem) to a difficult build of many small
>>jars.  I think the new MEME to be associated with Avalon would be "I
>>can't build it, I have no idea what it is or how useful it is".
>>
>
>Funny - I would have said the opposite. That used to be the old problem. 
>Given that I just tried to build ftpserver and it FAILED, then I tried 
>to build db and it FAILED, a few weeks ago I tried to build phoenix and it 
>passed but with CORRUPT jars, a week before that the same occured with 
>phoenix, and a week before that pheonix was also broken. 
>
>So exactly how is it easier to have these corruptions and failures?
>
With respect dude, I am not defending the previous position....

>I am TIRED of having to fix build problems that arise because people are 
>using jakarta-avalon/tools and those stupid build.* scripts. Look at all the 
>ugly hacks in the build files that are present to get around the failure of 
>that.
>
Agree.

>I have no problem putting some jars in CVS - especially ones of highly 
>"dynamic" projects. However things like xalan, xerces, ant, junit and so 
>forth should not be put in CVS because inevitably they will cause headaces 
>and incompatabiliteis - especially now that JDK1.4 includes xalan and crimson.
>
Agree.  

- Paul



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: ant.properties

Posted by Peter Donald <pe...@apache.org>.
On Fri, 29 Mar 2002 21:55, Paul Hammant wrote:
> We will have gone from a position of an easy build of a big jar (that
> itself being an acceptance problem) to a difficult build of many small
> jars.  I think the new MEME to be associated with Avalon would be "I
> can't build it, I have no idea what it is or how useful it is".

Funny - I would have said the opposite. That used to be the old problem. 
Given that I just tried to build ftpserver and it FAILED, then I tried 
to build db and it FAILED, a few weeks ago I tried to build phoenix and it 
passed but with CORRUPT jars, a week before that the same occured with 
phoenix, and a week before that pheonix was also broken. 

So exactly how is it easier to have these corruptions and failures?

I am TIRED of having to fix build problems that arise because people are 
using jakarta-avalon/tools and those stupid build.* scripts. Look at all the 
ugly hacks in the build files that are present to get around the failure of 
that.

I have no problem putting some jars in CVS - especially ones of highly 
"dynamic" projects. However things like xalan, xerces, ant, junit and so 
forth should not be put in CVS because inevitably they will cause headaces 
and incompatabiliteis - especially now that JDK1.4 includes xalan and crimson.

-- 
Cheers,

Pete

----------------------------------------------
Money is how people with no talent keep score.
----------------------------------------------

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: ant.properties

Posted by Jeff Turner <je...@socialchange.net.au>.
On Fri, Mar 29, 2002 at 10:55:19AM +0000, Paul Hammant wrote:
> Peter,
> 
> >
> >Most newbies aren't going to build everything at one pop. I know I haven't 
> >done it at all except to test that it works. I just go into the required 
> >product directory and type ant there. I think even newbies are capable of 
> >reading BUILDING.txt and comprehending it.
> >
> With respect, this fails the five second test.
> 
> We will have gone from a position of an easy build of a big jar (that 
> itself being an acceptance problem) to a difficult build of many small 
> jars.

Yes, but back then we didn't have dependencies like jmxri.jar for
baxter, and altrmi for instrument-client. As excalibur grows, this
problem gets worse.

> I think the new MEME to be associated with Avalon would be "I can't
> build it, I have no idea what it is or how useful it is".

Absolutely agree that users should be able to type 'ant' in the root,
and have something intelligible happen, not a compiler error.


--Jeff

> 
> - Paul
> 

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: ant.properties

Posted by Paul Hammant <Pa...@yahoo.com>.
Peter,

>
>Most newbies aren't going to build everything at one pop. I know I haven't 
>done it at all except to test that it works. I just go into the required 
>product directory and type ant there. I think even newbies are capable of 
>reading BUILDING.txt and comprehending it.
>
With respect, this fails the five second test.

We will have gone from a position of an easy build of a big jar (that 
itself being an acceptance problem) to a difficult build of many small 
jars.  I think the new MEME to be associated with Avalon would be "I 
can't build it, I have no idea what it is or how useful it is".

- Paul




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: ant.properties

Posted by Peter Donald <pe...@apache.org>.
On Fri, 29 Mar 2002 21:34, Paul Hammant wrote:
> Peter,
>
> >>If we did that, then in many cases, copying ant.properties wouldn't be
> >>necessary.
> >
> >Im not sure what you mean. I have one file at
> >jakartat-avalon-excalibur/ant.properties
> >
> >and that works fine.
>
> If you go frrom fresh CVS, and just invoke ant, then you'll see the
> newbies experience.  It is very daunting.  There are
> ant.properties.sample files all over the place and it is not easy to get
> going.  It deinately fails a five minute test.

Most newbies aren't going to build everything at one pop. I know I haven't 
done it at all except to test that it works. I just go into the required 
product directory and type ant there. I think even newbies are capable of 
reading BUILDING.txt and comprehending it.

-- 
Cheers,

Pete

----------------------------------------
Whatever you do will be insignificant, 
but it is very important that you do it. 
                              --Gandhi
----------------------------------------

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: ant.properties

Posted by Paul Hammant <Pa...@yahoo.com>.
Peter,

>>If we did that, then in many cases, copying ant.properties wouldn't be
>>necessary.
>>
>
>Im not sure what you mean. I have one file at 
>jakartat-avalon-excalibur/ant.properties
>
>and that works fine.
>

If you go frrom fresh CVS, and just invoke ant, then you'll see the 
newbies experience.  It is very daunting.  There are 
ant.properties.sample files all over the place and it is not easy to get 
going.  It deinately fails a five minute test.

- Paul





--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: ant.properties

Posted by Peter Donald <pe...@apache.org>.
On Fri, 29 Mar 2002 20:56, Jeff Turner wrote:
> A lot of our dependencies are within Excalibur. Eg, all/ now depends on
> instrument, concurrent and collections. How about we:

I think this interdependency web is just a temporary thing until all/ gets 
broken down down into more usable components.

>  - Write a build.xml target which builds dependent projects. So running
>    'ant' in all/ will also build it's dependencies.

+1

>  - Add <echo> messages to clearly indicate what's going on. Pete, at one
>    stage this mucked up your emacs regexes or something.. are you using
>    IDEA permanently now?;)

I use IDEA for th excalibur bits - still use emacs for phoenix though ;)

> If we did that, then in many cases, copying ant.properties wouldn't be
> necessary.

Im not sure what you mean. I have one file at 
jakartat-avalon-excalibur/ant.properties

and that works fine.

-- 
Cheers,

Pete

--------------------------------------------------
 Logic: The art of being wrong with confidence...
--------------------------------------------------

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: ant.properties

Posted by Jeff Turner <je...@socialchange.net.au>.
On Fri, Mar 29, 2002 at 09:40:45AM +0000, Paul Hammant wrote:
> Folks,
> 
> I am finding it difficult to complete the setup necessary to build 
> excalibur from scratch.  And I am not a newbie.

I'm also finding it difficult.

A lot of our dependencies are within Excalibur. Eg, all/ now depends on
instrument, concurrent and collections. How about we:

 - Hardcode correct defaults (../*/build/lib/whatever.jar) in the
   build.xml files. Or project.properties files, to follow the Turbine
   convention.
 - Write a build.xml target which builds dependent projects. So running
   'ant' in all/ will also build it's dependencies.
 - Add <echo> messages to clearly indicate what's going on. Pete, at one
   stage this mucked up your emacs regexes or something.. are you using
   IDEA permanently now?;)

If we did that, then in many cases, copying ant.properties wouldn't be
necessary.

--Jeff

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: ant.properties

Posted by Paul Hammant <Pa...@yahoo.com>.
Berin Loritsch wrote:

>We should not be using ant.properties.sample if we are depending
>on their contents.  We should have ant.properties in every excalibur
>product package.  The ".sample" is causing issues.
>
-1  People will have subsequent CVS update probs then.

>
>An alternative is to check for the existence of the file and copy
>the ant.properties.sample to ant.properties and load it.  That way
>we always have the property files we need to build excalibur, but
>we don't run into accidently checking in changes that only work on
>one machine.
>
+1

>
>>-----Original Message-----
>>From: Paul Hammant [mailto:Paul_Hammant@yahoo.com] 
>>Sent: Friday, March 29, 2002 4:41 AM
>>To: Avalon Development
>>Subject: ant.properties
>>
>>
>>Folks,
>>
>>I am finding it difficult to complete the setup necessary to build 
>>excalibur from scratch.  And I am not a newbie.
>>
>>Given that ant.properties is reuired in a number of places 
>>(or at least 
>>the properties they define are), I though the following may 
>>be useful if 
>>added to pertinent places of the build files :
>>
>>Index: build.xml 
>>===================================================================
>>RCS file: /home/cvs/jakarta-avalon-excalibur/all/build.xml,v
>>retrieving revision 1.118
>>diff -r1.118 build.xml
>>195c195,199
>><   <target name="check-datasource" depends="check-environment" 
>>if="datasource.present">
>>---
>> >   <target name="check-ant-properties" 
>>unless="excalibur-collections.home">
>> >      <fail message="You need an ant.properties to build 
>>excalibur.  
>>Either one in your home dir, or one the jakarta-avalon-excalibur/all 
>>dir. There is an ant.properties.sample that can be copied for 
>>this need."/>
>> >   </target>
>> >
>> >   <target name="check-datasource" depends="check-environment, 
>>check-ant-properties" if="datasource.present">
>>
>>Note that it is checking for a single property from each 
>>build file and 
>>not the presence of the local build file...
>>
>>Thoughts?
>>
>>- Paul
>>
>>
>>--
>>To unsubscribe, e-mail:   
>><mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
>>For 
>>additional commands, 
>>e-mail: <ma...@jakarta.apache.org>
>>
>
>
>--
>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: ant.properties

Posted by Berin Loritsch <bl...@apache.org>.
We should not be using ant.properties.sample if we are depending
on their contents.  We should have ant.properties in every excalibur
product package.  The ".sample" is causing issues.

An alternative is to check for the existence of the file and copy
the ant.properties.sample to ant.properties and load it.  That way
we always have the property files we need to build excalibur, but
we don't run into accidently checking in changes that only work on
one machine.

> -----Original Message-----
> From: Paul Hammant [mailto:Paul_Hammant@yahoo.com] 
> Sent: Friday, March 29, 2002 4:41 AM
> To: Avalon Development
> Subject: ant.properties
> 
> 
> Folks,
> 
> I am finding it difficult to complete the setup necessary to build 
> excalibur from scratch.  And I am not a newbie.
> 
> Given that ant.properties is reuired in a number of places 
> (or at least 
> the properties they define are), I though the following may 
> be useful if 
> added to pertinent places of the build files :
> 
> Index: build.xml 
> ===================================================================
> RCS file: /home/cvs/jakarta-avalon-excalibur/all/build.xml,v
> retrieving revision 1.118
> diff -r1.118 build.xml
> 195c195,199
> <   <target name="check-datasource" depends="check-environment" 
> if="datasource.present">
> ---
>  >   <target name="check-ant-properties" 
> unless="excalibur-collections.home">
>  >      <fail message="You need an ant.properties to build 
> excalibur.  
> Either one in your home dir, or one the jakarta-avalon-excalibur/all 
> dir. There is an ant.properties.sample that can be copied for 
> this need."/>
>  >   </target>
>  >
>  >   <target name="check-datasource" depends="check-environment, 
> check-ant-properties" if="datasource.present">
> 
> Note that it is checking for a single property from each 
> build file and 
> not the presence of the local build file...
> 
> Thoughts?
> 
> - Paul
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <ma...@jakarta.apache.org>
> 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>