Whatever the version you specify, the version from Maven core used at runtime is injected. If you don't use any new method (if a new method happens to have been added, which is not sure), there won't be any issue: that's the only risk by compiling with an newer Maven core library
This makes me think we could have done an Animal Sniffer signature for Maven APIs, but we didn't do it... Regards, Hervé Le vendredi 18 novembre 2016 11:12:30 UTC+1, Anders Hammar a écrit : > > I see that in mojo-parent 40 the maven-plugin-api has been bumped to v3.0. > For a plugin that is still compatible with Maven 2.2.1, would it be a > problem using that parent? > > /Anders > -- You received this message because you are subscribed to the Google Groups "mojohaus-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/6eb8ef5f-6fdb-4a5f-9eac-0fa39d31ebeb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
