Not sure if this would fit your needs:
- write a custome build logger and store the required information in a new file
- check the content of that file
Jan
package org.apache.ant;
import org.apache.tools.ant.*;
import java.io.*;
public class ResultBuildLogger extends DefaultLogger {
publi
Don't be confused by Ants output: the start of does not mean that Ant
wants to open the connection:
[get] Getting:
http://192.168.1.124:8081/nexus/content/groups/public//javassist/javassist/3.12.1.GA/javassist-3.12.1.GA.jar
[get] To: /home/usera/.m2/repository/javassist/javassist/
3.1
If I read the source of Ants main class [1] I would think, that the buildfile
must be a real file on the file system. It cannot be run from the classpath.
What do you expect from bundling the buildfile in a jar?
A workaround is using a "launcher buildfile" which extracts the content oft he
jar
Use
Jan
${time}
* inheritall="false" *
* inheritall="true" *
${nr}: ${time}
-Ursprüngliche N
I wouldnt start java programs via exec.
I modified the tutorial example a litte bit.
Basically you iterate with AntContrib over the JARs and start them via .
Jan
/src/oata/HelloWorld.java
package oata;
public class HelloWorld {
public static void main(String[] args) {
// Tutorial m
AFAIK there was some work in
http://svn.apache.org/repos/asf/ant/sandbox/historical/xdocs/
But I dont know any "official" tool.
Jan
-Ursprüngliche Nachricht-
Von: Bob Tarling [mailto:bobtarl...@hotmail.com]
Gesendet: Mittwoch, 26. September 2012 20:45
An: user@ant.apache.org
Betreff: I
