Groovy packaging
Your Groovy applications must meet specific packaging requirements before you can submit them for scanning.
See Supported languages and platforms for instructions for other platforms.
Supported Groovy versions
Language | Version | Compilers | Platform |
---|---|---|---|
Groovy | 2.4–2.6, 3.0 | groovyc 2.4–2.6, 3.0 targeted for JDK7+ | JVM 1.6–1.9, 10–15 |
Supported Groovy frameworks
Framework | Supported versions |
---|---|
Grails | 3.2–3.3, 4.0, 5.0 |
Compilation guidance
You can compile Groovy applications using either:
- The Grails command-line system
- IDEs that wrap Groovy and Grails, such as IntelliJ or the Groovy/Grails Tool Suite (GGTS)
You must compile and submit Groovy applications as JAR or WAR files. Submit debug symbols for as much of the application as possible.
If you build your project using Ant, you must turn on the debug
property in the javac
tasks, for example:
<javac debug="on"> ... set of classes
</javac>
Grails command-line settings
If you build your project with the Grails command line, change your current working directory to the Groovy application home directory. Run this command to produce the JAR or WAR file that you can upload to Veracode for analysis:
projectHome$ ./grailsw assemble
IntelliJ settings
If you build your project with IntelliJ IDEA, perform these actions in the IDE:
-
Build > Rebuild Project
-
Build > Make Grails Web Archive
When the actions complete, the
build/libs/
folder of the project home directory displays the WAR file that you can upload to Veracode for analysis.