Java 17 as a minimum requirement

[AnotherDeveloper]

Hi,

I already had a problem using a library which requires at least Java 11. Since now Maven is moving to Java 17, I suggest moving also to Java 17. They released a Release-Candidate end of last month, so I think a final version of Maven using Java 17 is imminent anyway.

Any thoughts on that?

[Benjamin Marwell]

Most of us here are Maven Developers, too! :)

That said, as long as we raise the major version and release maybe one beta version, I have no objections.

I think we should do that on the most common plugins.

But this also means we might need to maintain two versions (3.x and 4.x compatible) at the same time for a while, although the 3.x line could be maintained by (maybe) the funds:

https://github.com/support-and-care/maven-support-and-care

What do the others think of this?

[Jochen Wiedmann]

For the foreseeable future, Maven 3 will be the predominant version.
Even if it no longer is, a lot of people will still be using Maven 3
with older runtimes. I see no reason, why we should leave them behind.

Jochen


--
The woman was born in a full-blown thunderstorm. She probably told it
to be quiet. It probably did. (Robert Jordan, Winter's heart)

[Slawomir Jaranowski]

sobota, 14 grudnia 2024 o 21:35:05 UTC+1 bmar...@gmail.com napisał(a):

Most of us here are Maven Developers, too! :)

That said, as long as we raise the major version and release maybe one beta version, I have no objections.

I think we should do that on the most common plugins.

But this also means we might need to maintain two versions (3.x and 4.x compatible) at the same time for a while, although the 3.x line could be maintained by (maybe) the funds:

https://github.com/support-and-care/maven-support-and-care

What do the others think of this?

Maintaining two versions will bring more complications. We do not have many maintainers or contributors so for adding next work I don't see a benefit today.

I enabled builds by Maven 4 in many plugins to be sure that plugins can be used by Maven 4.

Benjamin thanks for mentioning support-and-care. Can you give me more
details on how mojohaus maintainers, contributors are  supported ...

Are there any rules about it? 

[Hervé Boutemy]

here is our existing strategy https://maven.apache.org/developers/compatibility-plan.html

for any plugin that is Maven 4 only, I don't see any problem with JDK 17: it's de-facto the prerequisite

for any plugin for Maven 3, it's Maven 3 compatibility that drives = JDK 8:

making sure that Maven 4 (on JDK 17) can run a Maven 3 plugin is a great idea to detect any unexpected incompatibility, but definitively it's the Maven 3 compatibility that drives the minimum JDK prerequisite

Regards,

Hervé

--
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 mojohaus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/mojohaus-dev/9ab3b334-ecfe-44bf-89b4-7bad45055e85n%40googlegroups.com.

[Slawomir Jaranowski]

What plugin project from mojohaus do you have in mind?

Should be discussed one by one.

>
> --
> 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 mojohaus-dev...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/mojohaus-dev/be290cb9-4aca-43ca-89e8-a646e1214970n%40googlegroups.com.



--
Sławomir Jaranowski

[Slawomir Jaranowski]

On Sat, 14 Dec 2024 at 21:35, Benjamin Marwell <bmar...@gmail.com> wrote:
>
> Most of us here are Maven Developers, too! :)
>
> That said, as long as we raise the major version and release maybe one beta version, I have no objections.
> I think we should do that on the most common plugins.
>
> But this also means we might need to maintain two versions (3.x and 4.x compatible) at the same time for a while, although the 3.x line could be maintained by (maybe) the funds:
> https://github.com/support-and-care/maven-support-and-care

Maintaining two versions will bring more complications.
We do not have many maintainers or contributors so for adding next
work I don't see a benefit today.
I enabled builds by Maven 4 in many plugins to be sure that plugins
can be used by Maven 4.

Benjamin thanks for mentioning support-and-care. Can you give me more
details on how mojohaus maintainers, contributors are supported ...
Are there any rules about it?


>

> What do the others think of this?
>
> AnotherDeveloper schrieb am Samstag, 14. Dezember 2024 um 14:42:29 UTC+1:
>
> Hi,
> I already had a problem using a library which requires at least Java 11. Since now Maven is moving to Java 17, I suggest moving also to Java 17. They released a Release-Candidate end of last month, so I think a final version of Maven using Java 17 is imminent anyway.
>
> Any thoughts on that?
>

> --
> 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 mojohaus-dev...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/mojohaus-dev/49cac187-a662-4bb1-b56f-c6b561f718d5n%40googlegroups.com.



--
Sławomir Jaranowski

[Jochen Wiedmann]

On Wed, Dec 18, 2024 at 12:47 PM Slawomir Jaranowski
<s.jara...@gmail.com> wrote:

> What plugin project from mojohaus do you have in mind?
>
> Should be discussed one by one.

Good point!

Jochen

[AnotherDeveloper]

I thought about the license-maven-plugin.

But by reading all your opinions on the update topic I'm not so sure any more that an update it's worth it.

Although: While the plugin inherits the mojo parent pom.xml, it overwrites some values specifically itself. Maybe this plugin is worth an exception?!

BTW: Some pom.xml values in the plugin were outdated, for my patch I had to update them, or I would run into problems with my integration tests.

Specifically the "version" of the "mojo-parent" was 77, not the current 86 and the "mavenVersion" property was still on 3.5.4, instead of the current agreed on 3.6.3.

Anyway, thanks for all the information so far.

On Wednesday, December 18, 2024 at 12:47:07 PM UTC+1 s.jara... wrote:

On Sat, 14 Dec 2024 at 14:42, 'AnotherDeveloper' via mojohaus-dev
>

> Hi,
> I already had a problem using a library which requires at least Java 11. Since now Maven is moving to Java 17, I suggest moving also to Java 17. They released a Release-Candidate end of last month, so I think a final version of Maven using Java 17 is imminent anyway.
>
> Any thoughts on that?

What plugin project from mojohaus do you have in mind?

Should be discussed one by one.

--

Sławomir Jaranowski

[Slawomir Jaranowski]

On Sun, 22 Dec 2024 at 12:54, 'AnotherDeveloper' via mojohaus-dev
<mojoha...@googlegroups.com> wrote:
>
> I thought about the license-maven-plugin.
> But by reading all your opinions on the update topic I'm not so sure any more that an update it's worth it.
> Although: While the plugin inherits the mojo parent pom.xml, it overwrites some values specifically itself. Maybe this plugin is worth an exception?!
>
> BTW: Some pom.xml values in the plugin were outdated, for my patch I had to update them, or I would run into problems with my integration tests.
> Specifically the "version" of the "mojo-parent" was 77, not the current 86 and the "mavenVersion" property was still on 3.5.4, instead of the current agreed on 3.6.3.

License plugin has the latest parent version .... and sets Maven
3.6.3 as the minimum version.
https://github.com/mojohaus/license-maven-plugin/blob/master/pom.xml

If you talk about another plugin ... parent should be updated.

>
> Anyway, thanks for all the information so far.
>
> On Wednesday, December 18, 2024 at 12:47:07 PM UTC+1 s.jara... wrote:
>
> On Sat, 14 Dec 2024 at 14:42, 'AnotherDeveloper' via mojohaus-dev
> >
> > Hi,
> > I already had a problem using a library which requires at least Java 11. Since now Maven is moving to Java 17, I suggest moving also to Java 17. They released a Release-Candidate end of last month, so I think a final version of Maven using Java 17 is imminent anyway.
> >
> > Any thoughts on that?
>
> What plugin project from mojohaus do you have in mind?
>
> Should be discussed one by one.
>
> --
> Sławomir Jaranowski
>

> --
> 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 mojohaus-dev...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/mojohaus-dev/c6c5447b-5356-4d3a-8ddd-7be4b5549963n%40googlegroups.com.



--
Sławomir Jaranowski

[Papst AufDrogen]

Sorry, my bad, I must have mixed something up with the updates. I updated my code and I'm just happy that everything is now on its latest versions.

Sorry again (I respond just now because I was basically on holiday last week).

To view this discussion visit https://groups.google.com/d/msgid/mojohaus-dev/CAGjJkv3PHsXc3HemJ0uRDiFr_NJg-zK-YzE24sBWO-LDGedKQQ%40mail.gmail.com.