The closest is ant -p (or ant -p -v to get more information). This won't list the target dependencies, but I don't see it as a problem: dependencies are not important for the end user (they just tell how the target works).
Up vote 1 down vote favorite share g+ share fb share tw.
Right now I just use a little power shell script to match lines that contain.
The closest is ant -p (or ant -p -v to get more information). This won't list the target dependencies, but I don't see it as a problem: dependencies are not important for the end user (they just tell how the target works). What's important is what the target does, which is what should be in its description: ... I what you really want is the target dependencies, then reading the xml file is the best you can do.
Thanks, this command is great – tjb Oct 11 '11 at 9:49.
No there isn't but you can do it like this : Where ${display.targets. Xsl} points to the following . Xsl file : Target : depends on : Description : And ${basedir}{build.
File} points to your current build. Xml file. The output will be something like this : xslt Loading stylesheet D:\Tools\StackOverFlow\test.
Xslt xslt xslt Target : build xslt xslt Target : modify. Trs xslt Description : Modifies . Trs file targets xslt xslt Target : regex depends on : modify.
Trs Depending on your build. Xml of course.
If you search for "ant dependency graph", you'll find some suggestions on how to produce a . Dot file from your build file which can be rendered into a visual graph by GraphViz.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.