You might want to try a few of your scenarios using evaluate, it might do what you are looking for. def stringMap = “[‘a’:2,’b’:4]” def map = evaluate(stringMap) assert map.a == 2 assert map.b == 4 def stringMapNested = “[‘foo’:’bar’, baz:[‘alpha’:’beta’]]” def map2 = evaluate(stringMapNested) assert map2.foo == “bar” assert map2.baz.alpha == “beta”
I think global properties should be avoided and gradle offers you a nice way to do so by adding properties to a task: task task1 { doLast { task1.ext.variable = “some value” } } task task2 { dependsOn task1 doLast { println(task1.variable) } }
I don’t know Scala, but in Java new BigDecimal(1.1) initializes the BigDecimal with a double value and thus it is not exactly equal to 1.1. In Java you have to use new BigDecimal(“1.1”) instead. Maybe that will help in Scala as well.
Maybe Groovy doesn’t have ‘native’ support for zip files, but it is still pretty trivial to work with them. I’m working with zip files and the following is some of the logic I’m using: def zipFile = new java.util.zip.ZipFile(new File(‘some.zip’)) zipFile.entries().each { println zipFile.getInputStream(it).text } You can add additional logic using a findAll method: def … Read more
Really-thorough unit tests are the most important technique (yes, I do always aim for 100% coverage), as they also catch many other typos (e.g. where I write + and meant -), off-by-one issues, etc. Integration and load tests exercising every feature are the second line of defense against all kinds of errors (mostly, though, deeper … Read more
This answer is purely supplemental to @PeterNiederwieser’s answer. In it he mentions that you can configure the name pattern used by Surefire. Here is an example of what worked for me: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.18</version> <configuration> <includes> <!– By default only files ending in ‘Test’ will be included, so also include support for Spock style … Read more