Sounds like a good idea for the site..
manfred
offbynull-maven wrote on 19.03.2015 22:03:
I understand that. But, shouldn't this be explicitly stated somewhere?
Some official guide somewhere essentially saying that if you're planning
on releasing your mojo publicly...
to support Maven2
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
If you can see where you would have liked this note to appear, you
should add it.
Documentation added by someone who was originally looking for the info
is much more likely to be in the right place.
Ron
On 20/03/2015 1:03 AM, offbynull-maven wrote:
I understand that. But, shouldn't this be
I understand that. But, shouldn't this be explicitly stated somewhere?
Some official guide somewhere essentially saying that if you're planning
on releasing your mojo publicly...
to support Maven2 you should be using JDK1.5 or lower (don't actually
know if this is correct)
to support
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: users-unsubscr...@maven.apache.org
For additional
How else will it work?
If you compile it into Java 8 byte-code, the Java 6 run-time is going to
have a tough time running it.
Ron
On 20/03/2015 12:31 AM, offbynull-maven wrote:
If the minimum JDK for Maven3 is JDK1.6, should my custom mojo always
be built against JDK1.6 or lower?
Are there
