On Thu, 31 Aug 2006, Jesse Glick <[EMAIL PROTECTED]> wrote:
> Stefan Bodewig wrote:
>> you'd just be asking for classloader problems if you have two
>> different versions of Ant inside the same Java VM while compiling
>> Ant or running the Unit tests, aren't you?
>
> This is another pet peeve of m
I know this too. To run ant testcases, either I run them
individually in IDEA, or I bootstrap and rebuild and install my new
version of ant, then run the tests.
I just set my ANT_HOME to point to ~/projects/ant-core-trunk/build/
dist - then I'm always running the latest code and the tests
Original-Nachricht
Datum: Fri, 1 Sep 2006 05:31:48 +0930
Von: "Stephen McConnell" <[EMAIL PROTECTED]>
An: "\'Ant Developers List\'"
Betreff: RE: Building Ant 1.7beta
> > This is another pet peeve of mine: apparently when you run
>
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jesse Glick
> Sent: Friday, 1 September 2006 4:56 AM
> To: dev@ant.apache.org
> Subject: Re: Building Ant 1.7beta
>
> Stefan Bodewig wrote:
> > you'd just be asking for clas
Stefan Bodewig wrote:
you'd just be asking for classloader problems if you have two different
versions of Ant inside the same Java VM while compiling Ant or running
the Unit tests, aren't you?
This is another pet peeve of mine: apparently when you run the Ant unit
tests, the version of Ant it
Jesse Glick wrote:
Stefan Bodewig wrote:
Sometimes we build new features that are useful enough to apply the
right away in Ant's own build file.
Obviously. But it seems to me that the convenience of the many users of
Ant (sources) outstrips the convenience of the few Ant developers. For
exam
> To Kev: surely most Ant committers work on at least one other Ant-based
> project where improvements can be seen? Or does the Apache Foundation
> pay your rent? :-)
:) I wish! I was (attempting humour) at suggesting that the ant
developers/committers only add stuff which helps to make the an
On Tue, 29 Aug 2006, Jesse Glick <[EMAIL PROTECTED]> wrote:
> Stefan Bodewig wrote:
>> Sometimes we build new features that are useful enough to apply the
>> right away in Ant's own build file.
>
> Obviously. But it seems to me that the convenience of the many users
> of Ant (sources) outstrips th
On Tue, 29 Aug 2006, Kev Jackson <[EMAIL PROTECTED]> wrote:
> OT slightly, does ant build maven in gump?
No. Well, for Maven 1 it tries but never managed to do so. I don't
think you can build Maven 2 with Ant at all, it bootstraps itself much
like Ant does.
Stefan
Hello Jesse,
when someone is developing ant inside an IDE, I believe that the
IDE's default functionality is good enough to work, because ant is
for the most part a java library.
you can modify ant classes in the IDE, then run the corresponding
JUnit tests, and you do not need all the boo
Bootstrapping works fine. Maybe there are bugs and it should be smarter, but
it seems reasonable.
- Alexey.
On 8/29/06, Jesse Glick <[EMAIL PROTECTED]> wrote:
Stefan Bodewig wrote:
> Sometimes we build new features that are useful enough to apply the
> right away in Ant's own build file.
Obvi
Stefan Bodewig wrote:
Sometimes we build new features that are useful enough to apply the
right away in Ant's own build file.
Obviously. But it seems to me that the convenience of the many users of
Ant (sources) outstrips the convenience of the few Ant developers. For
example, it is impossibl
On Mon, 28 Aug 2006, Jesse Glick <[EMAIL PROTECTED]> wrote:
> I've grumbled in the past that it is not very friendly for Ant trunk
> sources to be unbuildable by the current Ant release, but another
> committer (I forget now who) said this was intentional...?
Might have been me.
Sometimes we bui
Mark McKay wrote:
Apparently, ant 1.7 can't be built with ant 1.6.5.
No, it cannot.
I've grumbled in the past that it is not very friendly for Ant trunk
sources to be unbuildable by the current Ant release, but another
committer (I forget now who) said this was intentional...?
-J.
--
[EMA
I am glad it worked. There is also boostrap.bat script to be run in cmd.exe.
- Alexey.
On 8/26/06, Mark McKay <[EMAIL PROTECTED]> wrote:
Got it working after running bootstrap.sh. After that, the rest of your
commands worked. Thanks.
It would be really useful to point out to other naive fol
Got it working after running bootstrap.sh. After that, the rest of your
commands worked. Thanks.
It would be really useful to point out to other naive folks like me that
bootstrap.sh should be run to build ant. I went with the build.xml,
which seemed logical to me. The INSTALL and README f
Hi,
I'm using cygwin as well. The below commands aren't working. I'm also
not sure what you're getting at here. There is no directory named
/bootstrap, and even if there was, how could I run programs in it after
I deleted it?
Mark McKay
Alexey Solofnenko wrote:
The required files are i
The required files are in lib folder (without Xalan). This is what I just
ran (some commands are from Cygwin):
cd path-to-ant-svn
svn update
set JAVA_HOME=c:\jdk-full-path.
set ANT_HOME=
rm -rf bootstrap
.\bootstrap
.\bootstrap\bin\ant -f fetch.xml
.\bootstrap\bin\ant dist
- Alexey.
On 8/26
That didn't help much. Now I can no longer access Ant. When I try to
run build.bat, I get the following message:
$ build.bat
error: Missing required jar files.
The Ant tool is required. Download Ant from the following URL
http://jakarta.apache.org/ant/index.html and place the ant.jar
file in
I would guess you need to bootstrap new ANT. Remove ANT_HOME environment
variable and run bootstrap script.
- Alexey.
On 8/26/06, Mark McKay <[EMAIL PROTECTED]> wrote:
Hi,
I'm having trouble building Ant 1.7.0beta, and am wondering how to
either do it form the ant-core files on the svn reposi
20 matches
Mail list logo
