I do have a slightly off-topic gripe -- as of late, (in the rh snapshots), 
jboss-all/tools/bin/ant has not been executable on UNIX systems (took my 
little mind a while to figure out what was going on).  The 
jboss-all/build/build.sh script has been failing because of it.  It looks 
for an executable 'ant', but never finds it (it doesn't have the 
executable bit set).  I can see three possible solutions:

1. Just have the executable bit set on the ant script to start with
2. Change the search() function in build.sh to read like this:

search() {
    search="$*"
    for d in $search; do
        ANT_HOME="`pwd`/$d"
        ANT="$ANT_HOME/bin/ant"
          # ------ Begin modifications --------
          # If the file exists at all, attempt to add the executable bit
        if [ -e "$ANT" ]; then
            `chmod +x $ANT`
        fi
          # ------ End modifications --------
        if [ -x "$ANT" ]; then
            # found one
            echo $ANT_HOME
            break
        fi
    done
}
#(just added a -e test to see if the file exists, and attempt to make it 
executable so that the next -x test works)

3. Skip looking for an executable ant script -- just make sure it exists, 
and call it with 'sh ant'.

-jason





Jason Dillon <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
11/20/2001 09:38 PM

 
        To:     [EMAIL PROTECTED]
        cc:     [EMAIL PROTECTED]
        Subject:        [JBoss-dev] Re: [jboss-docs] Is the build system too 
complicated?



I have not found an easy way to provide this common setup/initialization 
stuff as a resource.  Perhaps if I could tell the JAXP parser to read a 
resource file when parsing this could be done, but that would require the 
Ant entity hooks to be installed to handle that.

Perhaps they have done that, perhaps I could sway them todo it... though 
my 
previous attempts to do so has failed (too much *ucking voting).

If you can think of a way please let me know.

Thanks for your feedback!

--jason


On Tue, 20 Nov 2001, David Jencks wrote:

> It has often seemed to me that there is substantial duplication between 
the
> setup parts of the module level build.xml files.  I sure haven't figured
> out a clue of a way to reduce this, but if it could be done, it might 
make
> the files a little less intimidating.  In light of the vast improvement
> over the preceding build "system", this is a hardly visible quibble.
> 
> david jencks
> 
> On 2001.11.20 16:43:07 -0500 Jason Dillon wrote:
> > Please let me know if you think that the build system is too 
complicated,
> > or 
> > if there is some part of the system which is too complicated.
> > 
> > --jason
> > 
> > 
> > 
> > ---------------------------------------------------------------
> > Subscribe: [EMAIL PROTECTED]
> > Unsubscribe:[EMAIL PROTECTED]
> > Archive: http://groups.yahoo.com/group/jboss-docs/ 
> > 
> > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
> > 
> > 
> > 
> > 
> > 
> 
> ------------------------ Yahoo! Groups Sponsor ---------------------~-->
> Universal Inkjet Refill Kit $29.95
> Refill any ink cartridge for less!
> Includes black and color ink.
> http://us.click.yahoo.com/Vv.L9D/MkNDAA/ySSFAA/9rHolB/TM
> ---------------------------------------------------------------------~->
> 
> ---------------------------------------------------------------
> Subscribe: [EMAIL PROTECTED]
> Unsubscribe:[EMAIL PROTECTED]
> Archive: http://groups.yahoo.com/group/jboss-docs/ 
> 
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
> 
> 


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development




_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to