So plugins *can* have a higher JDK requirement than the minimum version of Maven that they run against... hence http://maven.apache.org/plugin-tools/maven-plugin-plugin/report-mojo.html#requirements as a means to inform the user of the requirements.
Obviously it is nicer for the users of your plugin(s) if the minimum JDK is the same as the minimum for the lowest version of Maven that you support your plugin on... but there are cases where some plugins just have to go higher and retain an older version of Maven for other reasons (such as some noisy users that may not be able to upgrade maven but can upgrade JDK) On 20 March 2015 at 04:31, offbynull-maven <[email protected]> wrote: > If the minimum JDK for Maven3 is JDK1.6, should my custom mojo always be > built against JDK1.6 or lower? > > Are there any guidelines around this? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
