The groovy
command, which we introduced in the Executing Groovy code from the command line recipe, can also be used as a stream editor or text file filter. In this recipe, we will cover the -i
, -n
, and -p
parameters that can be used to leverage file editing and processing functionality.
Assume that you have a file, data.txt
, which contains five lines with numbers from 1
to 5
:
groovy -n -e "println line.toLong() * 2" data.txt
println
method call if we pass additional the -p
parameter to the command:groovy -n -p -e "line.toLong() * 2" data.txt
2 4 6 8 10
Due to the fact that we are using the -n
option, the code in double quotes is applied to each line read from the datafile specified as the last parameter in the command line. The line variable is predefined by Groovy, and you can use it to access, filter, or modify the line's content.
If you add the -i
option to the previous command, then it will actually modify the input file, with output values as follows:
groovy -i -n -p -e "line.toLong() * 2" data.txt
Adding a suffix .bak
to the -i
option will save the original input file data.txt
under data.txt.bak
:
groovy -i .bak -n -p -e "line.toLong() * 2" data.txt
You can use the -n
and -p
options to filter the input stream of other operating system commands. For example, if you want to filter the output of a directory listing command (dir
) to show only the *.jar
files, on Windows you can use the following command:
dir | groovy -n -e "if (line.contains('.jar')) println line"
Or on *nix-based operating systems, you can use the following command:
ls -la | groovy -n -e "if (line.contains('.jar')) println line"
Of course, the result of the previous commands can be easily achieved by more efficient operating system instructions. However, these examples are given to demonstrate that you can actually leverage the full power of the Groovy and Java programming languages to implement more complex processing rules.