These days I'm *only* coding in Groovy since it is such a nice, painless language and most of my GitHub code is in Groovy.
Groovy does a lot different than Java, one such difference is that you can now select what bytecode level to produce when building, this independent from the source. That is, the same source can be built for many different byte code levels without any changes in source code. You just select at what bytecode level you want the binary to be. I want to be able to build binaries for multiple bytecode levels and thus I'm doing this: <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> <modelVersion>4.0.0</modelVersion> <parent> <groupId>se.natusoft.seagull</groupId> <artifactId>Seagull-APIs</artifactId> <version>1.0.0</version> </parent> <artifactId>Seagull-Internal-APIs</artifactId> <version>${parent.version}_${bytecode.version}</version> This actually works! I do however get warnings about using variable expressions in version tag. Will this feature potentially go away in future versions of maven ? My goal is to be able to produce same code at different byte-code levels. By appending byte-code level in version I can produce multiple artifacts for different byte-code levels, in a relatively easy way. But if using variables in <version/> tag goes away then it becomes much more difficult. That it works now I see as a very nice and flexible feature. BR / Tommy ______________________ Tommy Svensson to...@natusoft.se
