ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conor MacNeill" <>
Subject Re: cvs commit: jakarta-ant/src/script ant ant.bat antRun antRun.bat lcp.bat
Date Tue, 23 Jan 2001 13:10:58 GMT
From: "Peter Donald" <>
> The problem is that junit.jar is not part of the primordial classloader
> thus unless we go jdk1.2+ specific with a context classloader there is no
> way for the junit task to see junit.jar at that point. We could make it
> part of the primordial classloader but that potential brings in a whole
> bunch of other pain.

What is that pain? With the old scripts I have been using junit.jar without
any problems

I want to type

build run-tests

and have it run the tests. This doesn't work at the moment.

> The base build is extremely controlled in what it can
> acces to avoid miscompiling basically.

Not sure of your point here.

> >The install targets have gone. I used these to promote a build from my
> >development area into my standard ANT_HOME area. Since I both develop
> >use ant I want to control over that. In other words ANT_HOME is NOT my
> >development area. I think being able to install like this is a good
> >and is common practice in make based projects (make install, etc)
> right. The way it should be done now is below and it will install it bu
> default (minus the docs)
> -Ddist.dir=/my/install/dir

This should be, IMHO

build install

This is what it used to be. I don't want to have to remember where I put
ANT_HOME and have to type it every time. I'm getting old so you need to
keep things simple for me, Pete.

If you look at the old build.bat it was implemented by calling bin/ant.bat.
It was very simple. I did this to reduce the duplication of code between
build.bat and ant.bat. Your changes mean that build.bat now duplicates a
large chunk of ant.bat and that is not a good thing, IMHO. If someone makes
a change in one, they need to remember to change the other.

The old build.bat was really about setting up an appropriate value of
ANT_HOME and the install targets. As a consequence, typing

ant install

would not clobber the currently running version of ant because the install
target defines were not set.

Anyway, there are some other problems:

build.bat resets the value of ANT_HOME. The old script restored the value.
I think this is the way to go.

Please turn echo back off again :-)

version info seems to have disappeared.

I tried
build dist -Ddist.dir=%ANT_HOME%

but it blows up with

Warning: skipping zip archive
F:\oss_ssh\JakartaSSH\jakarta-ant\ because no
files were included.
Nothing to do:
F:\oss_ssh\JakartaSSH\jakarta-ant\jakarta-ant-1.3alpha-bin.tar is up to
Building gzip:


F:\oss_ssh\JakartaSSH\jakarta-ant\build.xml:364: Problem creating gzip
F:\oss_ssh\JakartaSSH\jakarta-ant\jakarta-ant-1.3alpha-bin.tar (The system
cannot find the file specifie
F:\oss_ssh\JakartaSSH\jakarta-ant\jakarta-ant-1.3alpha-bin.tar (The system
cannot find the file specified)
        at Method)

Total time: 22 seconds

Anyway, got to get an early night tonight, so I'll catch up with this again


View raw message