Hi Glenn-

 

yes i was going to suggest a regular expression utility which reads these files 
to place the results in properties files 
then have your ant script read in the associated properties with the contents 
of the property file

globmapper seems like the better option..

 

Greetings and Salutations from the other side of the pond
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.Ce message est confidentiel et peut être 
privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec 
bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non 
autorisée ou la copie de ceci est interdite. Ce message sert à l'information 
seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant 
donné que les email peuvent facilement être sujets à la manipulation, nous ne 
pouvons accepter aucune responsabilité pour le contenu fourni.



 

> Date: Fri, 26 Mar 2010 17:09:22 -0500
> Subject: Re: I must be blind
> From: glenn...@gmail.com
> To: user@ant.apache.org
> 
> I think that doc is found at
> http://ant.apache.org/manual/conceptstypeslist.html
> 
> I find it a bit challenging, too.
> 
> --glenn
> 
> 
> On Fri, Mar 26, 2010 at 16:20, Robert Menteer <reet...@me.com> wrote:
> 
> > I'm looking over the documentation that comes with Apache Ant version 1.8.0
> > and can't find where classpath, path and pathelement are documented. I've
> > found a page that describes path like structures but it doesn't list the
> > valid attributes or nested elements for these. Another thing I can't find in
> > the documentation is a description of the relationships between filelist,
> > fileset, patternset and path and how to convert them back and forth. For
> > instance there has to be an easier way to compile only those classes in one
> > package while removing all class dependencies on the package classes and
> > update documentation.
> >
> > <!-- Get list of files in which we're interested. -->
> > <fileset id = "java.source.set"
> > dir = "${src}">
> > <include name = "**/Package/*.java" />
> > </fileset>
> >
> > <!-- Get a COMMA separated list of classes to compile. -->
> > <pathconvert property = "java.source.list"
> > refid = "java.source.set"
> > pathsep = ",">
> > <globmapper from = "${src}/*...@{src.extent}"
> > to = "*.class" />
> > </pathconvert>
> >
> > <!-- Remove ALL dependencies on package classes. -->
> > <depend srcdir = "${src}"
> > destdir = "${build}"
> > includes = "${java.source.list}"
> > closure = "yes" />
> >
> > <!-- Get a list of up to date classes. -->
> > <fileset id = "class.uptodate.set"
> > dir = "${build}">
> > <include name = "**/*.class" />
> > </fileset>
> >
> > <!-- Get list of source files for up to date classes. -->
> > <pathconvert property = "java.uptodate.list"
> > refid = "class.uptodate.set"
> > pathsep = ",">
> > <globmapper from="${build}/*.class" to="*.java" />
> > </pathconvert>
> >
> > <!-- Compile only those classes in package that are not up to date. -->
> > <javac srcdir = "${src}"
> > destdir = "${build}"
> > classpathref = "compile.classpath"
> > includes = "${java.source.list}"
> > excludes = "${java.uptodate.list}"/>
> >
> > <!-- Get list of directories of class files for package. --:
> > <pathconvert property = "class.dir.list"
> > refid = "java.source.set"
> > pathsep = ",">
> > <globmapper from = "${src}/*.java"
> > to = "${build}*" />
> > </pathconvert>
> >
> > <!-- Convert directory list to path. -->
> > <path id = "class.dirs.path">
> > <dirset dir = "${build}"
> > includes = "class.dir.list" />
> > </path>
> >
> > <!-- Update package documentation. -->
> > <jdepend outputfile = "${docs}/jdepend-report.txt">
> > <classpath refid = "compile.classpath" />
> > <classpath location = "${build}" />
> > <classespath>
> > <path refid = "class.dirs.path" />
> > </classespath>
> > <exclude name = "java.*" />
> > <exclude name = "javax.*" />
> > </jdepend>
> >
> >
> > Notice there's a number of conversions between filesets, paths and comma
> > separated list just to get the proper 'type' required for the different ant
> > tasks. Is there a way to simplify this while still processing the fewest
> > files in a complex directory structure?
> >
> >
> >
> >
                                          
_________________________________________________________________
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_3

Reply via email to