sobota, 14 grudnia 2024 o 21:35:05 UTC+1 [email protected] 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? 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 <https://maven.apache.org/docs/history.html>, 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/mojohaus-dev/9ab3b334-ecfe-44bf-89b4-7bad45055e85n%40googlegroups.com.
