maven-plugin

Maybe new warnings after upgrading ErrorProne in #3355.

/home/runner/work/jib/jib/jib-core/src/main/java/com/google/cloud/tools/jib/image/json/JsonToImageTranslator.java:250: warning: [UnrecognisedJavadocTag] This Javadoc tag wasn't recognised by the parser. Is it malformed somehow, perhaps with mismatched braces?
58

59
   * Converts a map of volumes strings to a set of {@link Absolut

Consider the following:

void meth(Closure closure) {
  closure.|
}

When invoking content assist (Ctrl+Space) at |, the methods and properties of groovy.lang.Closure are very low in the list of proposals. This is due to very-well-known type adjustments made within org.codehaus.groovy.eclipse.codeassist.proposals.AbstractGroovyProposal.getRelevanceClass().

Add 'since' information to plugin configuration parameters by inspecting the commit history.

We need to add more integration tests (living in the src/it folder) to cover various usage scenarios.

Right now we only have a single test that just checks that the plugin can run a basic test with no additional configuration (This can be used as an example on how to configure other integration tests). We should be testing various configuration options as well.

Requirements:

• The .jmx files

Description

These tests could be extracted into a parameterized test:

https://github.com/eclipse/jkube/

Currently, the headless scanner extension expects an XML based configuration file and this works ok. But, making the XML is cumbersome and also requires that most of the request URLs be wrapped in CDATA blocks.

IMHO, this would be much simpler, cleaner and much more concise in JSON than in XML, Also, the configuration files for Burp itself seem to be JSON based. So, this move will make it sor