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 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 Maven3.0 to 3.2 you should be using JDK1.6 or lower
to support Maven3.3+ you should be using JDK1.7 or lower
On 3/19/2015 9:47 PM, Ron Wheeler wrote:
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 any guidelines around this?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
