I am using Ant's <parallel> task to perform multiple simultaneous targets that use <exec> tasks, but it's difficult to read the output because it is interleaved. Is there any way to change the [exec] label that appears before each line of output to use the command or target name?
For example, while running pdepend and phpcpd I would like to change [exec] to [pdepend] and [phpcpd]:
pdepend:
[exec] PHP_Depend 0.10.5 by Manuel Pichler
[exec]
phpcpd:
[exec] Parsing source files:
[exec] phpcpd 1.3.2 by Sebastian Bergmann.
[exec]
[exec] ............................................................ 60
[exec] Found 26 exact clones with 640 duplicated lines in 28 files:
[exec]
[exec] - application/modules/controllers/IndexController.php:16-31
[exec] ............................................................ 120
[exec] application/modules/controllers/ErrorController.php:15-30
[exec]
[exec] - application/modules/controllers/PhotosController.php:24-33
[exec] ............................................................ 180
[exec] ............................................................ 240
becomes
pdepend:
[pdepend] PHP_Depend 0.10.5 by Manuel Pichler
[pdepend]
phpcpd:
[phpcpd] Parsing source files:
[phpcpd] phpcpd 1.3.2 by Sebastian Bergmann.
[phpcpd]
[pdepend] ............................................................ 60
[phpcpd] Found 26 exact clones with 640 duplicated lines in 28 files:
[phpcpd]
[phpcpd] - application/modules/controllers/IndexController.php:16-31
[pdepend] ............................................................ 120
[phpcpd] application/modules/controllers/ErrorController.php:15-30
[phpcpd]
[phpcpd] - application/modules/controllers/PhotosController.php:24-33
[pdepend] ............................................................ 180
[pdepend] ............................................................ 240
Have you tried setting the taskname attribute on the exec task? I'll double check in a couple of hours and confirm.
Update:
Yep, taskname does the trick. e.g.,
<exec executable="phpcpd" taskname="phpcpd">
...
</exec>
From Common Attributes of all Tasks:
taskname: A different name for this task instance - will show up in the logging output.
Related
I am trying to create a native installer for a java application. I have successfully used jpackage on OpenJDK/Linux, but now I am in Oracle JDK on Windows.
What I cannot believe is the error message: Why does jpackage claim that 'exe' is an unsupported type if the help page just list it as one of the allowed values? How come entering anything but 'app-image' leads to failure?
I am using the maven-antrun-plugin to execute this ant snippet:
<target>
<exec executable="jpackage" failonerror="true">
<arg line="--version"/>
</exec>
<exec executable="jpackage" failonerror="true">
<arg line="--help"/>
</exec>
<exec executable="jpackage" failonerror="true">
<arg line="--input target/dist"/>
<arg line="--main-jar ${project.artifactId}-${project.version}.jar"/>
<arg line="--main-class ${mainclass}"/>
<arg line="--dest target"/>
<arg line="--name ${project.artifactId}"/>
<arg line="--app-version ${project.version}"/>
<arg line="--type exe"/>
<arg line="--verbose"/>
</exec>
</target>
The build fails with this output (separated for the three tasks).
[exec] 16.0.1
[exec] Usage: jpackage <options>
[exec]
[exec] Sample usages:
[exec] --------------
[exec] Generate an application package suitable for the host system:
[exec] For a modular application:
[exec] jpackage -n name -p modulePath -m moduleName/className
[exec] For a non-modular application:
[exec] jpackage -i inputDir -n name \
[exec] --main-class className --main-jar myJar.jar
[exec] From a pre-built application image:
[exec] jpackage -n name --app-image appImageDir
[exec] Generate an application image:
[exec] For a modular application:
[exec] jpackage --type app-image -n name -p modulePath \
[exec] -m moduleName/className
[exec] For a non-modular application:
[exec] jpackage --type app-image -i inputDir -n name \
[exec] --main-class className --main-jar myJar.jar
[exec] To provide your own options to jlink, run jlink separately:
[exec] jlink --output appRuntimeImage -p modulePath -m moduleName \
[exec] --no-header-files [<additional jlink options>...]
[exec] jpackage --type app-image -n name \
[exec] -m moduleName/className --runtime-image appRuntimeImage
[exec] Generate a Java runtime package:
[exec] jpackage -n name --runtime-image <runtime-image>
[exec]
[exec] Generic Options:
[exec] #<filename>
[exec] Read options and/or mode from a file
[exec] This option can be used multiple times.
[exec] --type -t <type>
[exec] The type of package to create
[exec] Valid values are: {"app-image", "exe", "msi"}
[exec] If this option is not specified a platform dependent
[exec] default type will be created.
[exec] --app-version <version>
[exec] Version of the application and/or package
[exec] --copyright <copyright string>
[exec] Copyright for the application
[exec] --description <description string>
[exec] Description of the application
[exec] --help -h
[exec] Print the usage text with a list and description of each valid
[exec] option for the current platform to the output stream, and exit
[exec] --name -n <name>
[exec] Name of the application and/or package
[exec] --dest -d <destination path>
[exec] Path where generated output file is placed
[exec] Defaults to the current working directory.
[exec] (absolute path or relative to the current directory)
[exec] --temp <file path>
[exec] Path of a new or empty directory used to create temporary files
[exec] (absolute path or relative to the current directory)
[exec] If specified, the temp dir will not be removed upon the task
[exec] completion and must be removed manually
[exec] If not specified, a temporary directory will be created and
[exec] removed upon the task completion.
[exec] --vendor <vendor string>
[exec] Vendor of the application
[exec] --verbose
[exec] Enables verbose output
[exec] --version
[exec] Print the product version to the output stream and exit
[exec]
[exec] Options for creating the runtime image:
[exec] --add-modules <module name>[,<module name>...]
[exec] A comma (",") separated list of modules to add.
[exec] This module list, along with the main module (if specified)
[exec] will be passed to jlink as the --add-module argument.
[exec] if not specified, either just the main module (if --module is
[exec] specified), or the default set of modules (if --main-jar is
[exec] specified) are used.
[exec] This option can be used multiple times.
[exec] --module-path -p <module path>...
[exec] A ; separated list of paths
[exec] Each path is either a directory of modules or the path to a
[exec] modular jar.
[exec] (each path is absolute or relative to the current directory)
[exec] This option can be used multiple times.
[exec] --jlink-options <jlink options>
[exec] A space separated list of options to pass to jlink
[exec] If not specified, defaults to "--strip-native-commands
[exec] --strip-debug --no-man-pages --no-header-files"
[exec] This option can be used multiple times.
[exec] --runtime-image <file path>
[exec] Path of the predefined runtime image that will be copied into
[exec] the application image
[exec] (absolute path or relative to the current directory)
[exec] If --runtime-image is not specified, jpackage will run jlink to
[exec] create the runtime image using options:
[exec] --strip-debug, --no-header-files, --no-man-pages, and
[exec] --strip-native-commands.
[exec]
[exec] Options for creating the application image:
[exec] --icon <icon file path>
[exec] Path of the icon of the application package
[exec] (absolute path or relative to the current directory)
[exec] --input -i <input path>
[exec] Path of the input directory that contains the files to be packaged
[exec] (absolute path or relative to the current directory)
[exec] All files in the input directory will be packaged into the
[exec] application image.
[exec]
[exec] Options for creating the application launcher(s):
[exec] --add-launcher <launcher name>=<file path>
[exec] Name of launcher, and a path to a Properties file that contains
[exec] a list of key, value pairs
[exec] (absolute path or relative to the current directory)
[exec] The keys "module", "main-jar", "main-class",
[exec] "arguments", "java-options", "app-version", "icon", and
[exec] "win-console" can be used.
[exec] These options are added to, or used to overwrite, the original
[exec] command line options to build an additional alternative launcher.
[exec] The main application launcher will be built from the command line
[exec] options. Additional alternative launchers can be built using
[exec] this option, and this option can be used multiple times to
[exec] build multiple additional launchers.
[exec] --arguments <main class arguments>
[exec] Command line arguments to pass to the main class if no command
[exec] line arguments are given to the launcher
[exec] This option can be used multiple times.
[exec] --java-options <java options>
[exec] Options to pass to the Java runtime
[exec] This option can be used multiple times.
[exec] --main-class <class name>
[exec] Qualified name of the application main class to execute
[exec] This option can only be used if --main-jar is specified.
[exec] --main-jar <main jar file>
[exec] The main JAR of the application; containing the main class
[exec] (specified as a path relative to the input path)
[exec] Either --module or --main-jar option can be specified but not
[exec] both.
[exec] --module -m <module name>[/<main class>]
[exec] The main module (and optionally main class) of the application
[exec] This module must be located on the module path.
[exec] When this option is specified, the main module will be linked
[exec] in the Java runtime image. Either --module or --main-jar
[exec] option can be specified but not both.
[exec]
[exec] Platform dependent option for creating the application launcher:
[exec] --win-console
[exec] Creates a console launcher for the application, should be
[exec] specified for application which requires console interactions
[exec]
[exec] Options for creating the application package:
[exec] --app-image <file path>
[exec] Location of the predefined application image that is used
[exec] to build an installable package
[exec] (absolute path or relative to the current directory)
[exec] --file-associations <file path>
[exec] Path to a Properties file that contains list of key, value pairs
[exec] (absolute path or relative to the current directory)
[exec] The keys "extension", "mime-type", "icon", and "description"
[exec] can be used to describe the association.
[exec] This option can be used multiple times.
[exec] --install-dir <file path>
[exec] Relative sub-path under the default installation location
[exec] --license-file <file path>
[exec] Path to the license file
[exec] (absolute path or relative to the current directory)
[exec] --resource-dir <path>
[exec] Path to override jpackage resources
[exec] Icons, template files, and other resources of jpackage can be
[exec] over-ridden by adding replacement resources to this directory.
[exec] (absolute path or relative to the current directory)
[exec] --runtime-image <file-path>
[exec] Path of the predefined runtime image to install
[exec] (absolute path or relative to the current directory)
[exec] Option is required when creating a runtime package.
[exec]
[exec] Platform dependent options for creating the application package:
[exec] --win-dir-chooser
[exec] Adds a dialog to enable the user to choose a directory in which
[exec] the product is installed
[exec] --win-menu
[exec] Adds the application to the system menu
[exec] --win-menu-group <menu group name>
[exec] Start Menu group this application is placed in
[exec] --win-per-user-install
[exec] Request to perform an install on a per-user basis
[exec] --win-shortcut
[exec] Creates a desktop shortcut for the application
[exec] --win-upgrade-uuid <id string>
[exec] UUID associated with upgrades for this package
[exec] [22:46:46.538] Can not find WiX tools (light.exe, candle.exe)
[exec] [22:46:46.529] Running candle.exe
[exec] [22:46:46.538] Download WiX 3.0 or later from https://wixtoolset.org and add it to the PATH.
[exec] [22:46:46.539] jdk.jpackage.internal.PackagerException: Error: Invalid or unsupported type: [exe]
[exec] at jdk.jpackage/jdk.jpackage.internal.Arguments.generateBundle(Arguments.java:658)
[exec] at jdk.jpackage/jdk.jpackage.internal.Arguments.processArguments(Arguments.java:538)
[exec] at jdk.jpackage/jdk.jpackage.main.Main.execute(Main.java:98)
[exec] at jdk.jpackage/jdk.jpackage.main.Main.main(Main.java:52)
So why am I getting that error? And how can I fix it?
So as it seems the solution to the misleading error message
Error: Invalid or unsupported type: [exe]
had been on the screen all the time:
[exec] [22:46:46.538] Can not find WiX tools (light.exe, candle.exe)
[exec] [22:46:46.529] Running candle.exe
[exec] [22:46:46.538] Download WiX 3.0 or later from https://wixtoolset.org and
add it to the PATH.
After doing exactly that jpackage is behaving a lot better now.
I am experimenting with Jenkins and Ant. I would like to simply run my Makefile that does everything, the build and the tests.
I figured out that the best way is to use Ant because I become flexible with my build process similarly to travis.yml.
Unfortunately the compiler I am using only exists on Windows so I installed Jenkins on Windows. I wrote this build.xml
<?xml version="1.0"?>
<project name="Hello World Project" default="info">
<target name="info">
<echo>Hello World - Welcome to Apache Ant!</echo>
<exec executable="make"/>
</target>
</project>
And the output I get so far is this one:
C:\Program Files (x86)\Jenkins\workspace\test>exit 0
[test] $ cmd.exe /C "ant.bat info && exit %%ERRORLEVEL%%"
Unable to locate tools.jar. Expected to find it in C:\Program Files\Java\jre1.8.0_131\lib\tools.jar
Buildfile: C:\Program Files (x86)\Jenkins\workspace\test\build.xml
info:
[echo] Hello World - Welcome to Apache Ant!
[exec] rm -f test_*.s
[exec] arm-none-eabi-gcc.exe -O2 -Wall -S -c test.c -o test_gcc.s
[exec] make: arm-none-eabi-gcc.exe: Command not found
[exec] make: *** [Makefile:9: test_gcc.s] Error 127
[exec] Result: 2
BUILD SUCCESSFUL
Total time: 0 seconds
Finished: SUCCESS
Why do I get a BUILD SUCCESSFUL status while I got an Error?
N.B. I know I have to configure my PATH to include the toolchain. I would like to first understand this inconsistency.
By default, Ant's exec task does not fail the build when an error code is returned. However, this can simply be switched on with the failonerror attribute:
<exec executable="make" failonerror="true" />
I want to compile JNA library on 32-bit Cygwin or on 32-bit Debian Linux using -Dskip-native=false parameter. I installed the required packages, but it can't be compiled. It can be compiled on 64-bit Cygwin or 64-bit Debian Linux without any problem (for 64-bit target), but can't be compiled on 32-bit platforms. I also tried to compile the sources on jna-4.2.1/dist/src-full folder, but it couldn't be compiled.
I use the following parameters for 32-bit target.
export ANT_OPTS="-d32 -Dos.prefix=win32-x86 -Dskip-native=false"
I got the following error messages on 64-bit Cygwin (using the same parameters).
[exec] /cygdrive/d/Projects/jna-4.2.1/dist/src-full/native/libffi/src/x86/win64.S: Assembler messages:
[exec] /cygdrive/d/Projects/jna-4.2.1/dist/src-full/native/libffi/src/x86/win64.S:286: Error: bad register name `%r11'
[exec] /cygdrive/d/Projects/jna-4.2.1/dist/src-full/native/libffi/src/x86/win64.S:288: Error: bad register name `%rcx'
[exec] /cygdrive/d/Projects/jna-4.2.1/dist/src-full/native/libffi/src/x86/win64.S:291: Error: bad register name `%rsp)'
[exec] /cygdrive/d/Projects/jna-4.2.1/dist/src-full/native/libffi/src/x86/win64.S:294: Error: bad register name `%r11'
...
[exec] /cygdrive/d/Projects/jna-4.2.1/dist/src-full/native/libffi/src/x86/win64.S:516: Error: bad register name `%rbp'
[exec] /cygdrive/d/Projects/jna-4.2.1/dist/src-full/native/libffi/src/x86/win64.S:517: Error: unsupported instruction `ret'
[exec] /cygdrive/d/Projects/jna-4.2.1/dist/src-full/native/libffi/src/x86/win64.S:518: Warning: zero assumed for missing expression
[exec] /cygdrive/d/Projects/jna-4.2.1/dist/src-full/native/libffi/src/x86/win64.S:518: Warning: zero assumed for missing expression
[exec] Makefile:1345: recipe for target 'src/x86/win64.lo' failed
[exec] make[3]: Leaving directory '/cygdrive/d/Projects/jna-4.2.1/dist/src-full/build/native-win32-x86/libffi'
[exec] Makefile:1603: recipe for target 'all-recursive' failed
[exec] make[2]: Leaving directory '/cygdrive/d/Projects/jna-4.2.1/dist/src-full/build/native-win32-x86/libffi'
[exec] Makefile:741: recipe for target 'all' failed
[exec] make[1]: Leaving directory '/cygdrive/d/Projects/jna-4.2.1/dist/src-full/build/native-win32-x86/libffi'
[exec] Makefile:449: recipe for target '../build/native-win32-x86/libffi/.libs/libffi.a' failed
[exec] make[3]: *** [src/x86/win64.lo] Error 1
[exec] make[2]: *** [all-recursive] Error 1
[exec] make[1]: *** [all] Error 2
[exec] make: *** [../build/native-win32-x86/libffi/.libs/libffi.a] Error 2
BUILD FAILED
D:\Projects\jna-4.2.1\dist\src-full\build.xml:813: exec returned: 2
I get the following errors on 32-bit Cygwin.
[echo] os.prefix=win32-x86
[echo] os.name=Windows 7
[echo] os.arch=x86 (little)
[echo] build=build
[echo] build.native=D:\Projects\jna-4.2.1\dist\src-full\build\native-win32-x86
-setup:
compile:
[javac] Compiling 59 source files to D:\Projects\jna-4.2.1\dist\src-full\build\classes
[javac] warning: [options] bootstrap class path not set in conjunction with -source 1.6
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 warning
javah:
-native-api-check:
:rsrc:
rsrc:
[copy] Copying 1 file to D:\Projects\jna-4.2.1\dist\src-full\build\native-win32-x86
native:
[exec] Generating configure
[exec] autoreconf-2.69: Entering directory `.'
[exec] autoreconf-2.69: configure.ac: not using Gettext
[exec] autoreconf-2.69: running: aclocal --force -I m4
[exec] autoreconf-2.69: configure.ac: tracing
[exec] autoreconf-2.69: running: libtoolize --copy --force
[exec] libtoolize: putting auxiliary files in '.'.
[exec] libtoolize: copying file './ltmain.sh'
[exec] libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
[exec] libtoolize: copying file 'm4/libtool.m4'
[exec] libtoolize: copying file 'm4/ltoptions.m4'
[exec] libtoolize: copying file 'm4/ltsugar.m4'
[exec] libtoolize: copying file 'm4/ltversion.m4'
[exec] libtoolize: copying file 'm4/lt~obsolete.m4'
[exec] autoreconf-2.69: running: /usr/bin/autoconf-2.69 --force
[exec] autoreconf-2.69: running: /usr/bin/autoheader-2.69 --force
[exec] autoreconf-2.69: running: automake --add-missing --copy --force-missing
[exec] Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake-1.15 line 3936.
[exec] configure.ac:31: installing './compile'
[exec] configure.ac:19: installing './missing'
[exec] Makefile.am: installing './depcomp'
[exec] Configuring libffi (x86)
[exec] autoreconf-2.69: Leaving directory `.'
[exec] checking build system type... i686-pc-cygwin
[exec] checking host system type... i686-pc-cygwin
[exec] checking target system type... i686-pc-cygwin
[exec] checking for gsed... sed
[exec] checking for a BSD-compatible install... /usr/bin/install -c
[exec] checking whether build environment is sane... yes
[exec] checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
[exec] checking for gawk... gawk
[exec] checking whether make sets $(MAKE)... yes
[exec] checking whether make supports nested variables... yes
[exec] checking for gcc... i686-pc-mingw32-gcc
[exec] checking whether the C compiler works... no
[exec] configure: error: in `/cygdrive/d/Projects/jna-4.2.1/dist/src-full/build/native-win32-x86/libffi':
[exec] configure: error: C compiler cannot create executables
[exec] See `config.log' for more details
[exec] Makefile:449: recipe for target '../build/native-win32-x86/libffi/.libs/libffi.a' failed
[exec] make: *** [../build/native-win32-x86/libffi/.libs/libffi.a] Error 77
BUILD FAILED
D:\Projects\jna-4.2.1\dist\src-full\build.xml:813: exec returned: 2
Total time: 50 seconds
I couldn't understand why it says "[exec] checking whether the C compiler works... no" although I installed all development packages and lib packages on 32-bit Cygwin and although gcc works.
How can I compile jna's native libraries for 32-bit platforms?
According to config.log, configure is failing here:
/cygdrive/d/Projects/jna-4.2.1/native/libffi/configure: line 3927: i686-pc-mingw32-gcc: command not found
Make sure that your cross compiler is on your path or add CC=/path/to/your-cross-compiler to FFI_CONFIG.
I use Silk4J and in my build, I have to start the agent. The command I use is:
<exec spawn="true" executable="${env.OPEN_AGENT_HOME}/agent/openAgent.exe" />
It gives me this error
The ' characters around the executable and arguments are not part of the command.
Do I need to change it?
The message doesn't signify an error.
When the -v, -verbose, -d, or -debug option is given to Ant, the <exec> task outputs the command it is executing along with the message:
[exec] Current OS is Windows 7
[exec] Executing 'cmd' with arguments:
[exec] '/c'
[exec] '#for %a in (C:\src\ant\ant-dir-file-local) do #echo %~ta'
[exec]
[exec] The ' characters around the executable and arguments are
[exec] not part of the command.
[exec] 10/23/2013 02:36 AM
Breaking down the above example...
[exec] Executing 'cmd' with arguments:
^ ^
[exec] '/c'
^ ^
[exec] '#for %a in (C:\src\ant\ant-dir-file-local) do #echo %~ta'
^ ^
In this case, the single quotes (') above each ^ aren't part of the command. Ant wraps the executable name and each argument with single quotes to make it clear what is part of the command and what isn't. Ant does this to help users debug their Ant scripts when <exec> doesn't behave as expected. The message is purely informational.
It is good practice to wrap logged entries in single quotes so that if an entry is empty you can still see it, for example:
No password for user ''
Otherwise you would see:
No password for user
which is misleading.
In this case it only informs you that the quotes are only there for this reason and not part of the logged data. I think the sentence is slightly confusing because of the negative form 'are not part of the command' which looks like there is a problem...
It is purely informative. It is there to indicate that the apostrophe (') symbol you see above is not actually within the command that has been used.
It just "quotes" the string tokens you used in your command.
Example:
[exec] Current OS is Windows 10
[exec] Output redirected to property: git.timestamp
[exec] Executing 'cmd.exe' with arguments:
[exec] '/c'
[exec] 'git'
[exec] 'show'
[exec] '-s'
[exec] '--format=%ct'
[exec]
[exec] The ' characters around the executable and arguments are
[exec] not part of the command.
This indicates that you used /c git show -s --format=%ct inside cmd, and you can see that from the '/c', 'git' tokens. It just tells you to ignore the ' symbol. What it actually used is the git, show, -ss, etc. tokens in a chain, forming a full command.
This is fallible information for ant. Please note, that this error will result in a returned status code of "1", exiting your build as failed. It is not merely "purely informative" as the previous poster has stated. This part of the java invoked Runtime.exec() methods which ant implements. Overrides include the parameters (String command, args[]), and also (String cmdLine).
The following ANT exec tag does not behave as expected.
<exec executable="c:\scratch\test.cmd">
<arg value="A,B,C"/>
</exec>
When executed, I would expect this to call text.cmd with 1 argument. However, the arg is being expanded to three separate arguments.
As per the Manual, value is supposed to pass the contents as a single argument, however, it is passed as three (one for each component of the string separated by a comma).
I tried replacing the command "," with a semicolon (;) but this does not work either. It appears as if arg's value attribute parses the supplied string as if it were a path, which it is not.
Anyone know how to the "A,B,C" to pass as one argument?
For the sake of completeness, my test.cmd file is this:
#echo off
echo Arg1: %1
echo Arg2: %2
echo Arg3: %3
echo Arg4: %4
echo Arg5: %5
echo Arg6: %6
echo Arg7: %7
echo Arg8: %8
echo Arg9: %9
and the output of the ant build is:
[exec] Arg1: A
[exec] Arg2: B
[exec] Arg3: C
[exec] Arg4:
[exec] Arg5:
[exec] Arg6:
[exec] Arg7:
[exec] Arg8:
[exec] Arg9:
Issue has been resolved. I was so focused on the issue being in ant, that I didn't take the time to test how DOS like command lines interpret the command-line arguments.
from Window command line, I ran test.cmd a,c,b and see that the command argument was split, therefore, the issue is not related to ant. so now I just need to figure out how to force ANT to quote the arguments.
Try:
<exec executable="c:\scratch\test.cmd">
<arg line="A,B,C"/>
</exec>
See ant manual for description of how arguments work.