Command line to call to build. The build is run in another process.
There is a special command line to run ant internally within this VM rather than an external process in a new VM.
internal-ant [build-file] [target1] [target2] [target3] ...
This may execute your ant scripts faster because a new process does not have to be created.
However, there are limitations:
build-file must be the absolute path to the build filebuild-file and target names cannot have spaces in them.Command line to call to build.
Command line to call to build. The build is run in another process.
There is a special command line to run ant internally within this VM rather than an external process in a new VM.
internal-ant [build-file] [target1] [target2] [target3] ...
This may execute your ant scripts faster because a new process does not have to be created.
However, there are limitations:
build-file must be the absolute path to the build filebuild-file and target names cannot have spaces in them.Run build process
Run build process
See this atricle for more info.
List of events passed in by org.mashupbots.socko.buildtools.DirectoryWatcher
Runs an ant build internally.
Runs an ant build internally. Maybe a little faster than forking a new process.
See: http://www.ibm.com/developerworks/websphere/library/techarticles/0502_gawor/0502_gawor.html http://stackoverflow.com/questions/3684279/invoke-ant-programmatically-using-java-with-parameter http://stackoverflow.com/questions/6386349/call-ant-build-through-java-code http://thilosdevblog.wordpress.com/2010/08/30/calling-an-ant-target-via-java/
Responsible for running the build file
Command line to call to build. The build is run in another process.
There is a special command line to run ant internally within this VM rather than an external process in a new VM.
This may execute your ant scripts faster because a new process does not have to be created.
However, there are limitations:
build-filemust be the absolute path to the build filebuild-fileand target names cannot have spaces in them.