[antlr-interest] antlr 2.7.2 release candidate 2 available

[Sander Mägi]

Hi,

Maybe there are other concerns about licenses and redistributions, but at
the place I work we have found it very useful just to include the ant
libraries (427Kb) inside each of our internal project.

So no matter what project you checkout you can be sure you can just type
build.sh (or build.bat) and it builds - also no hassles for project
requiring some specific version of ant etc...

We began to use this way when we had to patch ant's tar task to get a bugfix
we needed very quickly - I guess ant has matured by now so these problems do
not exist any more but haven't seen reason to change the system because
extra 427Kb does not hurt anybody nowadays.

Just my 0.02 EUR,
Sander Mägi

----- Original Message -----
From: "Matt Benson" <gudnabrsam at yahoo.com>
To: <antlr-interest at yahoogroups.com>
Sent: Monday, January 06, 2003 4:52 PM
Subject: Re: [antlr-interest] antlr 2.7.2 release candidate 2 available


> I think any build process will be fine as long as it's
> simple to execute, which I believe, after portability,
> is the main fascination of Ant.  People don't mind
> working a bit at setup (to a point) if it means
> convenience later.  If you've got simplicity and
> portability then you ought not to find too many
> dissenters.
>
> -Matt
>
>
> --- Terence Parr <parrt at jguru.com> wrote:
> > Folks,
> >
> > I have updated the download area with rc2 that has
> > the updated
> > documentation and so on.  I have not yet responded
> > to a few problems
> > reported by you folks, but I wanted to get the doc
> > up and also to test
> > my new build procedure.
> >
> > I don't like having to download yet another tool
> > just to build
> > something (e.g., Ant or python).  Further, XML
> > should not be used for
> > human consumption (e.g., Ant).  What I want is a
> > stupid build script
> > that just compiles everything and then jar's it up.
> > When it only takes
> > a few seconds to rebuild the whole 50k line program,
> > why on earth would
> > we bother with dependencies and other junk.  Problem
> > is that scripts
> > are not portable...Java is however.  So, I added a
> > simple means for
> > ANTLR to self-compile and build a jar.  package
> > antlr/build has a
> > simple Tool in it that lets me say:
> >
> > java antlr.build.Tool build
> >
> > This uses property antlr.build.root to figure out
> > where the antlr dir
> > associated with the antlr package resides.  It
> > defaults to "." (current
> > directory).  You may also set the compiler as in:
> >
> > java -Dantlr.build.compiler=jikes antlr.build.Tool
> > build
> >
> > I have tested this on win2k (cmd shell and bash from
> > GNU) and Mac OS X.
> > Further, I have removed all of the build shell
> > scripts and mkjar type
> > scripts I had since there is only one all
> > encompassing antlr.jar now
> > (450k) and a self-
> > build tool.  Main dir is now clear of my build
> > stuff...just C++ and C#
> > stuff in there now.
> >
> > I'm assuming there will be an uproar over my
> > introducing yet another
> > build type thing, but having ANTLR build itself just
> > makes sense and
> > doesn't depend on anything else.
> >
> > Oh, the build procedure ignores antlr/util package
> > as I have stuff in
> > there I'm not sure is ready for prime time and
> > depends on my groovy
> > StringTemplate stuff.  I'll probably just remove
> > this for this release.
> >
> > Ter
> > --
> > Co-founder, http://www.jguru.com
> > Creator, ANTLR Parser Generator:
> > http://www.antlr.org
> > Lecturer in Comp. Sci., University of San Francisco
> >
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.com/info/terms/
> >
> >
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>


 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/