Yes! Didn't we already decide on this? Or was it Java 7 even?
/Anders
On Wed, Sep 9, 2015 at 8:25 AM, Hervé BOUTEMY wrote:
> Hi,
>
> I'm preparing to make a release of Maven Parnet POM once MPIR 2.8.1 is out
> (since MPIR-300 is required).
>
> This release will require
On 9 September 2015 at 16:02, Anders Hammar wrote:
> Yes! Didn't we already decide on this? Or was it Java 7 even?
>
Didn't we also write the decision down somewhere too?
I think
https://maven.apache.org/developers/java5.html
https://maven.apache.org/developers/java6.html
Hi,
I'm preparing to make a release of Maven Parnet POM once MPIR 2.8.1 is out
(since MPIR-300 is required).
This release will require Maven 3: projects with upgraded parent pom won't be
able to be built with Maven 2.2.1 any more.
One question: should we upgrade to Java 6?
Regards,
Hervé
don't hesitate to update the pom
for Java 6, the idea is to make a general update, while updating Maven 3
prerequisite
If no objection, I'll add this update to the release, with MPOM-84
Regards,
Hervé
Le mercredi 9 septembre 2015 15:10:31 Dan Tran a écrit :
> it is worth to pick up latest
it is worth to pick up latest release plugin 2.5.2 and gpg-plugin 1.6?
Thanks
-D
On Tue, Sep 8, 2015 at 11:46 PM, Barrie Treloar wrote:
> On 9 September 2015 at 16:02, Anders Hammar wrote:
>
> > Yes! Didn't we already decide on this? Or was it Java 7