You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Dan Warburton <wa...@tgf.tc.faa.gov> on 2000/05/25 14:33:25 UTC
make clean equivalent
So I just checked out and built Ant. We keep our source, classes and
html in the same tree. I'd like to
create a "make clean" equivalent.
deltree and delete don't seem to be the right tasks....
I worked with exec:
<target name="clean" depends="init">
<exec dir="${srcdir}" command="rm -r *class" os="Linux"
output="build.txt"
This generally works, but does not delete classes associated with inner
classes....
These are left behind after ant clean:
orion{warb}-> ls *class
XmlSimEventImporter$ActionElement.class
XmlSimEventImporter$ElementProcessor.class
XmlSimEventImporter$PredicateElement.class
XmlSimEventImporter$SimEventElement.class
XmlSimEventImporter$SimEventObjectElement.class
XmlSimEventImporter$UnknownElement.class
P.s. Is there a mailing list archive?
--
System Simulation Support Branch, ACT-510
TGF (Target Generation Facility, an Air Traffic Control Simulator)
FAA Technical Center, Atlantic City International Airport, NJ
08405 Mail Stop ACT-510 Phone: 609-485-4480
Dan Warburton warb@tgf.tc.faa.gov
Re: make clean equivalent
Posted by Stefan Bodewig <bo...@bost.de>.
>>>>> "JP" == John Pappin <jo...@jmonkey.com> writes:
JP> Why not add an include/exclude tag to the deltree task? (if its
JP> not already there).
Yes, this is what I've thought, too. It is not there. I've allready
started making deltree inherit from MatchingTask - give me some time -
so no duplicate effort is needed.
Stefan
Re: make clean equivalent
Posted by John Pappin <jo...@jmonkey.com>.
Why not add an include/exclude tag to the deltree task? (if its not already there).
- Brill
----- Original Message -----
From: Dan Warburton
To: ant-dev@jakarta.apache.org
Sent: Thursday, May 25, 2000 8:33 AM
Subject: make clean equivalent
So I just checked out and built Ant. We keep our source, classes and html in the same tree. I'd like to
create a "make clean" equivalent.
deltree and delete don't seem to be the right tasks....
I worked with exec:
<target name="clean" depends="init">
<exec dir="${srcdir}" command="rm -r *class" os="Linux" output="build.txt"
This generally works, but does not delete classes associated with inner classes....
These are left behind after ant clean:
orion{warb}-> ls *class
XmlSimEventImporter$ActionElement.class
XmlSimEventImporter$ElementProcessor.class
XmlSimEventImporter$PredicateElement.class
XmlSimEventImporter$SimEventElement.class
XmlSimEventImporter$SimEventObjectElement.class
XmlSimEventImporter$UnknownElement.class
P.s. Is there a mailing list archive?
--
System Simulation Support Branch, ACT-510
TGF (Target Generation Facility, an Air Traffic Control Simulator)
FAA Technical Center, Atlantic City International Airport, NJ
08405 Mail Stop ACT-510 Phone: 609-485-4480
Dan Warburton warb@tgf.tc.faa.gov
RE: Long Property Values
Posted by Jason Sando <js...@think1up.com>.
It seems obvious now but it just didn't occur to me.
Thanks!
-j
> -----Original Message-----
> From: Mariusz Nowostawski [mailto:mariusz@marni.otago.ac.nz]
> Sent: Thursday, May 25, 2000 2:50 PM
> To: ant-dev@jakarta.apache.org
> Subject: Re: Long Property Values
>
> I am doing what I use to do in shell scripts, and I sort of have nothing
> against it, but it could be done nicer, I reckon. There is heaps of
> repeating, but it is pretty readable:
>
>
> <property name="classpath" value="${java.home}/lib/rt.jar" />
>
> <property name="classpath" value="${classpath}:../lib/xml.jar" />
> <property name="classpath" value="${classpath}:../lib/jsdk.jar" />
> <property name="classpath" value="${classpath}:../lib/javalib.jar" />
> <property name="classpath" value="${classpath}:../lib/binkco.jar" />
> <property name="classpath" value="${classpath}:../lib/ecs-1.2.jar" />
> <property name="classpath" value="${classpath}:../lib/ifxjdbc.jar" />
> <property name="classpath" value="${classpath}:../lib/junit.jar" />
>
Re: Long Property Values
Posted by Mariusz Nowostawski <ma...@marni.otago.ac.nz>.
I am doing what I use to do in shell scripts, and I sort of have nothing
against it, but it could be done nicer, I reckon. There is heaps of
repeating, but it is pretty readable:
<property name="classpath" value="${java.home}/lib/rt.jar" />
<property name="classpath" value="${classpath}:../lib/xml.jar" />
<property name="classpath" value="${classpath}:../lib/jsdk.jar" />
<property name="classpath" value="${classpath}:../lib/javalib.jar" />
<property name="classpath" value="${classpath}:../lib/binkco.jar" />
<property name="classpath" value="${classpath}:../lib/ecs-1.2.jar" />
<property name="classpath" value="${classpath}:../lib/ifxjdbc.jar" />
<property name="classpath" value="${classpath}:../lib/junit.jar" />
On Thu, 25 May 2000, Jason Sando wrote:
> Is there any way to break up a long <property> tag? My "classpath" property
> ends up wrapping or going off the screen:
>
> <property name="classpath"
> value="${java.home}/lib/rt.jar:../lib/xml.jar:../lib/jsdk.jar:../lib/javalib
> .jar:../lib/binkco.jar:../lib/ecs-1.2.jar:../lib/ifxjdbc.jar:../lib/junit.ja
> r" />
>
> Thanks,
>
> -j
>
Long Property Values
Posted by Jason Sando <js...@think1up.com>.
Is there any way to break up a long <property> tag? My "classpath" property
ends up wrapping or going off the screen:
<property name="classpath"
value="${java.home}/lib/rt.jar:../lib/xml.jar:../lib/jsdk.jar:../lib/javalib
.jar:../lib/binkco.jar:../lib/ecs-1.2.jar:../lib/ifxjdbc.jar:../lib/junit.ja
r" />
Thanks,
-j
RE: [PATCH] deltree as MatchingTask (was Re: make clean equivalent)
Posted by Jason Sando <js...@think1up.com>.
I posted a similar patch on 5/4 that got no direct response.
-j
> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@bost.de]
> Sent: Thursday, May 25, 2000 7:41 AM
> To: ant-dev@jakarta.apache.org
> Subject: [PATCH] deltree as MatchingTask (was Re: make clean equivalent)
>
>
> I will followup on the other mails soon.
>
> This patch will make deltree a MatchingTask which means you can
> specify
>
> <deltree dir="src">
> <include name="**/*.class" />
> </deltree>
>
> and it should delete all the .class files in src (and all empty
> directories as well).
>
> Note that you now might have to explicitly disable default excludes
> to get the old behavior of deltree (maybe this should be the
> default?).
>
> No documentation patches for now as the part about directory based
> tasks needs a brush up.
>
> Stefan
>
>
[PATCH] deltree as MatchingTask (was Re: make clean equivalent)
Posted by Stefan Bodewig <bo...@bost.de>.
I will followup on the other mails soon.
This patch will make deltree a MatchingTask which means you can
specify
<deltree dir="src">
<include name="**/*.class" />
</deltree>
and it should delete all the .class files in src (and all empty
directories as well).
Note that you now might have to explicitly disable default excludes
to get the old behavior of deltree (maybe this should be the
default?).
No documentation patches for now as the part about directory based
tasks needs a brush up.
Stefan