[GitHub] [maven-shared-incremental] dependabot[bot] merged pull request #10: Bump maven-shared-components from 36 to 37
dependabot[bot] merged PR #10: URL: https://github.com/apache/maven-shared-incremental/pull/10 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-shared-incremental] dependabot[bot] merged pull request #5: Bump maven-shared-utils from 0.7 to 3.3.4
dependabot[bot] merged PR #5: URL: https://github.com/apache/maven-shared-incremental/pull/5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Resources Plugin 3.3.0 released
Subject: [ANN] Maven Resources Plugin 3.3.0 released The Apache Maven team is pleased to announce the release of the Maven Resources Plugin version 3.3.0. https://maven.apache.org/plugins/maven-resources-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-resources-plugin 3.3.0 Release Notes - Maven Resources Plugin - Version 3.3.0 ** Bug * [MRESOURCES-237] - Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior * [MRESOURCES-265] - Resource copying not using specified encoding * [MRESOURCES-268] - java.nio.charset.MalformedInputException: Input length = 1 * [MRESOURCES-269] - Symlinks cause copying resources to fail * [MRESOURCES-273] - Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0 * [MRESOURCES-275] - valid location for directory parameter is always required ** New Feature * [MRESOURCES-250] - Add ability to flatten folder structure into target directory when copying resources ** Task * [MRESOURCES-277] - Update plugin (requires Maven 3.2.5+) * [MRESOURCES-283] - Require Java 8 ** Dependency upgrade * [MRESOURCES-282] - Upgrade maven-plugin parent to 36 * [MRESOURCES-286] - Upgrade Maven Filtering to 3.3.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Question - JDK Minimum of future Apache Maven 4.0.0
> On Jul 25, 2022, at 12:34 PM, Michael Osipov wrote: > > Am 2022-07-25 um 21:31 schrieb Ralph Goers: >> So my vote would be +1 for Maven 4 requiring Java 17 under the condition >> that Maven 3 continues to get new releases. > > This will not happen with me, only patches if necessary 3.9.1, etc. As soon > as 4 is stable, 3 will be phased out. We don't have the resources for that. > So for 3.8.x. As soon as 3.9.0 gets out, or 3.9.1, 3.8.x will not receive any > fixes. > This is exactly what I expected as Maven has never supported older major releases once the new one is stable. Given that, I believe it would be a mistake to require Java 17, Ralph - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Question - JDK Minimum of future Apache Maven 4.0.0
Am 2022-07-25 um 21:31 schrieb Ralph Goers: So my vote would be +1 for Maven 4 requiring Java 17 under the condition that Maven 3 continues to get new releases. This will not happen with me, only patches if necessary 3.9.1, etc. As soon as 4 is stable, 3 will be phased out. We don't have the resources for that. So for 3.8.x. As soon as 3.9.0 gets out, or 3.9.1, 3.8.x will not receive any fixes. M - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Question - JDK Minimum of future Apache Maven 4.0.0
Some statistics below. I think you are being very optimistic about how fast
people will adopt JDK 17. If it follows the trends for Java 8 and 11 I would
put money on betting it won’t be the predominant version until the next LTS is
released.
https://adoptium.net/support and
https://aws.amazon.com/about-aws/whats-new/2020/08/amazon-corretto-8-11-support-extended/
shows Java 8 being supported through at least 2026 and Java 11 until 2027. I
don’t think users will be in a hurry to upgrade.
So if Maven were to continue enhancements and support for Maven 3 I don’t think
there would be any issue with making Maven 4 require Java 17. But the Maven
project doesn’t have a history of maintaining two major versions simultaneously
While lots of company’s are cautious in upgrading the JDK they are using,
generally they are less reluctant to upgrade Maven. But if Maven 4 requires
Java 17, most places won’t upgrade to it if they are using Java 8 or 11.
Although the -release option should guarantee compatibility I am sure lots of
folks won’t trust that it is.
So my vote would be +1 for Maven 4 requiring Java 17 under the condition that
Maven 3 continues to get new releases.
Ralph
https://newrelic.com/resources/report/2022-state-of-java-ecosystem#:~:text=More%20than%2048%25%20of%20applications,using%20the%20version%20in%20production.
https://www.infoworld.com/article/3652408/java-8-still-dominates-but-java-17-wave-is-coming-survey.html
> On Jul 23, 2022, at 12:05 PM, Enno Thieleke
> wrote:
>
> Fwiw:
>
> Romain, I think you're exaggerating. The answer is, like in most cases: "it
> depends".
>
> Most people, we're most likely talking 95-99% here, will happily use JDK 17
> with Maven 4.
>
> Some people might need to compile for lower sources and targets, but running
> tests for those builds in JDK 17 instead of, let's say 11, _will suffice in
> most cases_.
>
> Yes, there will be edge cases where people will be forced to use different
> JDKs at least for tests, some even for builds. But that's possible, so they
> won't get left behind.
>
> Regarding mvnd: It's not a silver bullet. It never was and it never will be.
> Whenever a build spawns new JVMs (for tests or other tasks), it doesn't
> benefit from mvnd anymore (in as much as it would without spawning new JVMs).
>
> To not use the latest (LTS) JDK in order to "better" support the 1-5% of the
> Maven users, who're still using obsolete JVMs (I'm obviously referring to
> Karl's assumption, which I agree with), would be a kick in the teeth of all
> Maven developers, who finally want to embrace the present (not even the
> future).
>
> Long story short, +1 for JDK 17 as minimum for Maven 4.
>
> Kind regards,
> Enno
>
>
> From: Romain Manni-Bucau
> Sent: Saturday, July 23, 2022 6:55 PM
> To: Maven Developers List
> Subject: Re: Question - JDK Minimum of future Apache Maven 4.0.0
>
> Le sam. 23 juil. 2022 à 17:25, Benjamin Marwell a
> écrit :
>
>> No, 2 JDKs are not required by default. Only if you use --release={<17} and
>> don't trust running tests on 17 are the same as running tests on 8.
>> Yes, there are changes (certificates, XML libs, rhino, etc).
>>
>
> As explained it means you dont write a single test or dont care of the test
> results so yes it needs 2 jdk.
>
>
>
>> So, for most projects that's probably not needed. For those who think it is
>> needed, I don't have a lot of pity. But it will be a requirement for quite
>> a few commercial projects, like Containers (JavaEE, as they will need to be
>> Java 8 as long as 2030ish due to extended support contracts).
>>
>> That said, I'm still thinking Java 17 will be a sane default.
>>
>>
>> On Sat, 23 Jul 2022, 10:50 Delany, wrote:
>>
>>> Using mvnd with toolchains doesn't improve the situation, in fact
>>> toolchains seem to invalidate any benefit of using mvnd.
>>> Even if this was resolved, is it fair to require mvnd?
>>> Delany
>>>
>>>
>>> On Sat, 23 Jul 2022 at 10:17, Mark Derricutt wrote:
>>>
Is that due to cold starting the JVM each time?
I wonder if mvnd supports toolchains effectively? Or if that could be
>> an
avenue to try.
--
"Great artists are extremely selfish and arrogant things" — Steven
>>> Wilson,
Porcupine Tree
On 23/07/2022 at 8:13:23 PM, Delany
>> wrote:
> I tried toolchains but dropped it because of the exorbitant
>> performance
> costs.
> A multi-module build that normally built in 3:50 took 10:34, and
>> that's
> with toolchaining only maven-compiler-plugin.
>
>
>
>>>
>>
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Question - JDK Minimum of future Apache Maven 4.0.0
Am 2022-07-25 um 20:54 schrieb Elliotte Rusty Harold: On Wed, Jul 20, 2022 at 1:39 PM Karl Heinz Marbaise wrote: Enterprise customers are extremely hesitant to upgrade. They often prefer to deploy a system once and never redeploy or change it ever after. Many insist on the bare minimum of absolutely necessary changes once they've got something working. I'm sure there are projects out there building on Java 17, but I personally have encountered zero of them. The projects I see on a daily basis are a mix of 8, 10, and 11 with an occasional Java 7 project hiding out somewhere in the depths of the enterprise or in a mobile app. I can absolutely confirm both observations from $work. If the application works it won't be touched all the time since there is zero benefit. Same for us. M - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Question - JDK Minimum of future Apache Maven 4.0.0
On Wed, Jul 20, 2022 at 1:39 PM Karl Heinz Marbaise wrote: > > Hi, > > On 20.07.22 13:04, Romain Manni-Bucau wrote: > > So you run tests with java 17? This is not what you want if your prod is > > in java 8, you can still get surprises so you need toolchain in your > > build (same happen for compilation since bytecode is not 1-1, only > > signatures). > > First what kind of surprises? > > Second can you show an example of different bytes codes? > I'm not sure if this is what was being talked about or not, but I absolutely have seen multiple extremely obscure breakages from Java 8 to Java 9+. Three areas in particular have bitten me: 1. There's a particularly nasty problem I've hit a few times involving the change in return types somewhere in java.nio. The details escape me at the moment. I only recall that when I see a certain error message I should google it to recall what it is. I think this is an example: https://jira.mongodb.org/browse/JAVA-2559 2. sun.misc.Unsafe and some other widely used parts of the undocumented APIs 3. The Java Module system, particularly split packages. E.g. https://github.com/grpc/grpc-java/issues/3522 The Java 8 to Java 9+ transition is painful, and a lot of products have not made that shift. For instance, Google Cloud's externally facing libraries, the majority of which are built with Maven, all have to support Java 8. Last I checked many still supported Java 7. Maybe that will finally change this year. It was only with a huge amount of painstaking customer by customer effort that GCP dropped support for Java 6 a couple of years ago. Enterprise customers are extremely hesitant to upgrade. They often prefer to deploy a system once and never redeploy or change it ever after. Many insist on the bare minimum of absolutely necessary changes once they've got something working. I'm sure there are projects out there building on Java 17, but I personally have encountered zero of them. The projects I see on a daily basis are a mix of 8, 10, and 11 with an occasional Java 7 project hiding out somewhere in the depths of the enterprise or in a mobile app. -- Elliotte Rusty Harold elh...@ibiblio.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resolver version 1.8.2
Am 2022-07-25 um 19:23 schrieb Michael Osipov: Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12351875 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Resolver Staging repo: https://repository.apache.org/content/repositories/maven-1790/ https://repository.apache.org/content/repositories/maven-1790/org/apache/maven/resolver/maven-resolver/1.8.2/maven-resolver-1.8.2-source-release.zip Source release checksum(s): maven-resolver-1.8.2-source-release.zip c873699bd3238d4eec65dc2c4da4f20d4fc1e205ee9b81b4126c3ab65daeb04dbc11016c80bdc38430ba82ce6b69c8bc5e91745f7be900d4ce26ffa682964c5d Staging site: https://maven.apache.org/resolver-archives/resolver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resolver version 1.8.2
+1 On Mon, Jul 25, 2022, 19:23 Michael Osipov wrote: > Hi, > > We solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12351875 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Resolver > > Staging repo: > https://repository.apache.org/content/repositories/maven-1790/ > > https://repository.apache.org/content/repositories/maven-1790/org/apache/maven/resolver/maven-resolver/1.8.2/maven-resolver-1.8.2-source-release.zip > > Source release checksum(s): > maven-resolver-1.8.2-source-release.zip > > c873699bd3238d4eec65dc2c4da4f20d4fc1e205ee9b81b4126c3ab65daeb04dbc11016c80bdc38430ba82ce6b69c8bc5e91745f7be900d4ce26ffa682964c5d > > Staging site: > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
[GitHub] [maven-shared-incremental] dependabot[bot] opened a new pull request, #10: Bump maven-shared-components from 36 to 37
dependabot[bot] opened a new pull request, #10: URL: https://github.com/apache/maven-shared-incremental/pull/10 Bumps [maven-shared-components](https://github.com/apache/maven-parent) from 36 to 37. Release notes Sourced from https://github.com/apache/maven-parent/releases;>maven-shared-components's releases. 37 What's Changed [MPOM-317] Upgrade fluido skin to 1.11.0 by https://github.com/slawekjaranowski;>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/66;>apache/maven-parent#66 Bump maven-pmd-plugin from 3.16.0 to 3.17.0 by https://github.com/dependabot;>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/64;>apache/maven-parent#64 [MPOM-322] Add ASF Data Privacy by https://github.com/slawekjaranowski;>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/65;>apache/maven-parent#65 [MPOM-324] Drop Social Media Plug-ins from documentation by https://github.com/slawekjaranowski;>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/67;>apache/maven-parent#67 [MPOM-331] Upgrade Surefire to 3.0.0-M7 by https://github.com/slachiewicz;>@slachiewicz in https://github-redirect.dependabot.com/apache/maven-parent/pull/68;>apache/maven-parent#68 [MPOM-334] Upgrade fluido skin to 1.11.1 by https://github.com/slawekjaranowski;>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/70;>apache/maven-parent#70 Bump maven-toolchains-plugin from 3.0.0 to 3.1.0 by https://github.com/dependabot;>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/69;>apache/maven-parent#69 Bump extra-enforcer-rules from 1.5.1 to 1.6.0 by https://github.com/dependabot;>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/71;>apache/maven-parent#71 Bump apache from 26 to 27 by https://github.com/dependabot;>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/72;>apache/maven-parent#72 Full Changelog: https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37;>https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37 Commits See full diff in https://github.com/apache/maven-parent/commits;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Resolver version 1.8.2
Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12351875 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Resolver Staging repo: https://repository.apache.org/content/repositories/maven-1790/ https://repository.apache.org/content/repositories/maven-1790/org/apache/maven/resolver/maven-resolver/1.8.2/maven-resolver-1.8.2-source-release.zip Source release checksum(s): maven-resolver-1.8.2-source-release.zip c873699bd3238d4eec65dc2c4da4f20d4fc1e205ee9b81b4126c3ab65daeb04dbc11016c80bdc38430ba82ce6b69c8bc5e91745f7be900d4ce26ffa682964c5d Staging site: https://maven.apache.org/resolver-archives/resolver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Resources Plugin version 3.3.0
Hi, The vote has passed with the following result: +1: Hervé Boutemy, Michael Osipov, Olivier Lamy PMC quorum: reached I will promote the artifacts to the central repo, the source release ZIP file and add this release the board report.
JDK 19: Rampdown Phase 2 + JavaOne
Greetings! JDK 19 is now in Rampdown Phase Two [1]. The overall feature set is frozen. Per the JDK Release Process [2] we now turn our focus to P1 and P2 bugs, which can be fixed with approval [3]. Late enhancements are still possible, with approval, but the bar is now extraordinarily high [4]. Given the current state of affairs, it is a good time to start testing your project(s) on JDK 20 Early-Access builds. To conclude, please make sure to check the heads-up below, including the one covering JavaOne! [1] https://mail.openjdk.org/pipermail/jdk-dev/2022-July/006803.html [2] https://openjdk.org/jeps/3 [3] https://openjdk.org/jeps/3#Fix-Request-Process [4] https://openjdk.org/jeps/3#Late-Enhancement-Request-Process ## Heads-up - JavaOne is back! After a long hiatus, JavaOne is back! From October 17-20 in Las Vegas, JavaOne will be jam-packed with hundreds of valuable and actionable sessions directly from the experts: learning sessions, tutorials, hands-on labs, lightning talks, panels, an unconference, BoF's, etc. The full JavaOne content catalog will be released soon. In the meantime, make sure to check https://inside.java/javaone/ for more updates. And if you are planning to attend JavaOne, please ping me. I'd like to meet you in person to chat over OpenJDK and the Quality Outreach program. And the drinks will be on me! ## Heads-up - JavaFX Media enhancements survey The JavaFX team is conducting a short survey [5] to gather input on potential JavaFX Media enhancements. The process is quite simple as the feedback will be collected via the openjfx-dev [6] mailing list. So if you are using JavaFX, make sure to raise your voice. [5] https://mail.openjdk.org/pipermail/openjfx-dev/2022-July/034949.html [6] https://mail.openjdk.org/mailman/listinfo/openjfx-dev ## JDK 19 JDK 19 Early-Access builds 32 are now available [7], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [8]. [7] https://jdk.java.net/19/ [8] https://jdk.java.net/19/release-notes ### JEPs integrated to JDK 19: - JEP 405: Record Patterns (Preview) - JEP 422: Linux/RISC-V Port - JEP 424: Foreign Function & Memory API (Preview) - JEP 425: Virtual Threads (Preview) - JEP 426: Vector API (4th Incubator) - JEP 427: Pattern Matching for switch (3rd Preview) - JEP 428: Structured Concurrency (Incubator) ### Recent changes that maybe of interest: - JDK-8289127: Apache Lucene triggers: DEBUG MESSAGE: duplicated predicate failed which is impossible - JDK-8290596: Update java.net.InetAddress to Detect Ambiguous IPv4 Address Literals - JDK-8290615: Remove the Alternate ThreadLocal Implementation of the Subject::current and Subject::callAs APIs - JDK-8290417: CDS cannot archive lamda proxy with useImplMethodHandle - JDK-8287809: Revisit implementation of memory session - JDK-8289278: Suspend/ResumeAllVirtualThreads need both can_suspend and can_support_virtual_threads - JDK-8288589: Files.readString ignores encoding errors for UTF-16 - JDK-8288425: Footprint regression due MH creation when initializing StringConcatFactory ## JDK 20 JDK 20 Early-Access builds 7 are now available [9], and are provided under the GNU General Public License v2, with the Classpath Exception. [9] https://jdk.java.net/20/ ### Recent changes that maybe of interest: - JDK-8264999: GeneralPath.lineTo() to itself produces jagged lines [Logged by Apache PDFBox] - JDK-8284997: arm32 build crashes since JDK-8283326 [Logged by JaCoCo] - JDK-8286101: Support formatting in @value tag - JDK-8289260: BigDecimal movePointLeft() and movePointRight() do not follow their API spec - JDK-8287835: Add support for additional float/double to integral conversion for x86 - JDK-8283091: Support type conversion between different data sizes in SLP - JDK-8288573: Make Executable.getParameterCount() actually abstract - JDK-8266670: Better modeling of access flags in core reflection - JDK-8290601: Update java.net.InetAddress to Detect Ambiguous IPv4 Address Literals - JDK-8290334: Update FreeType to 2.12.1 - JDK-8286030: Avoid JVM crash when containers share the same /tmp dir - JDK-8289743: AArch64: Clean up patching logic - JDK-8288107: Auto-vectorization for integer min/max - JDK-8274235: -Xshare:dump should not call vm_direct_exit ## Topics of Interest: * What is OpenJDK? - Inside Java Newscast https://inside.java/2022/06/30/insidejava-newscast-028/ * “Towards Generational ZGC!” - Inside Java Podcast https://inside.java/2022/06/29/podcast-024/ * HotSpot Deep Dive - Safepoint https://inside.java/2022/07/12/hotspot-deep-dive-safepoint/ * Introduction to Project Panama - Part 2: Variadic Functions https://inside.java/2022/06/27/introduction-to-project-panama-part-2/ * Data-Oriented Programming - Inside Java Newscast https://inside.java/2022/07/14/insidejava-newscast-029/ * Launching 10 millions virtual threads with Loom - JEP Café
[ANN] Maven Site Plugin 4.0.0-M3 released
The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 4.0.0-M3. https://maven.apache.org/plugins/maven-site-plugin/ Release Notes - Maven Site Plugin - Version 4.0.0-M3 ** Dependency upgrade * [MSITE-905] - Upgrade Doxia and Maven Reporting stack * [MSITE-906] - Upgrade plugins and components Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resources Plugin version 3.3.0
I missed to add +1 On Mon, 25 Jul 2022 at 21:35, Michael Osipov wrote: > Am 2022-07-25 um 08:44 schrieb Olivier Lamy: > > any idea why we now have the tests.jar here > > > https://repository.apache.org/content/repositories/maven-1789/org/apache/maven/plugins/maven-resources-plugin/3.3.0/ > > whereas it's not in previous versions? > > Here: > > https://github.com/apache/maven-resources-plugin/blob/1a9702fb763d2a783f98233b8f84e6580592715f/pom.xml#L211-L224 I know the test jar produced within the run-its profile But it was not present in 3.2.0 https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/3.2.0/ and we do not need it to attach it as it's only used by it tests (just an improvement) anyway not a problem but weird it was not in 3.2.0 but 3.1.0 > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Resources Plugin version 3.3.0
Am 2022-07-25 um 08:44 schrieb Olivier Lamy: any idea why we now have the tests.jar here https://repository.apache.org/content/repositories/maven-1789/org/apache/maven/plugins/maven-resources-plugin/3.3.0/ whereas it's not in previous versions? Here: https://github.com/apache/maven-resources-plugin/blob/1a9702fb763d2a783f98233b8f84e6580592715f/pom.xml#L211-L224 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Site Plugin version 4.0.0-M3
Hi, The vote has passed with the following result: +1: Michael Osipov, Slawomir Jaranowski, Sylwester Lachiewicz, Olivier Lamy, Herve Boutemy PMC quorum: reached I will promote the artifacts to the central repo, the source release ZIP file and add this release the board report. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resources Plugin version 3.3.0
any idea why we now have the tests.jar here https://repository.apache.org/content/repositories/maven-1789/org/apache/maven/plugins/maven-resources-plugin/3.3.0/ whereas it's not in previous versions? On Mon, 25 Jul 2022 at 16:34, Herve Boutemy wrote: > +1 > > Reproducible Builds near fully ok: reference build done on Windows with > JDK 8 > the only lille issue is for maven-resources-plugin-3.3.0-tests.jar that > contains a > unit/test-dir/resourceSystemProperties_Filtering/target/classes/file4.txt > file containing current working directory (current-working-directory = > D:\\Entwicklung\\Projekte\\maven-resources-plugin\\target\\checkout in the > reference build) > I'll open a Jira issue to try to improve that in a future release > > Regards, > > Hervé > > On 2022/07/23 18:08:08 Michael Osipov wrote: > > Hi, > > > > We solved 11 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317827=12348676 > > > > There are still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOURCES%20AND%20resolution%20%3D%20Unresolved > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1789/ > > > https://repository.apache.org/content/repositories/maven-1789/org/apache/maven/plugins/maven-resources-plugin/3.3.0/maven-resources-plugin-3.3.0-source-release.zip > > > > Source release checksum(s): > > maven-resources-plugin-3.3.0-source-release.zip > > sha512: > > > c7df1d5713d08c942d2f6b3a1b3d8463e3b5ef284470bb0efc2bbb241c5f224747e43007c9af6bdef82d4e220d926dbf490a959b6c290bc9c0106db70fc74752 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-resources-plugin-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Resources Plugin version 3.3.0
+1 Reproducible Builds near fully ok: reference build done on Windows with JDK 8 the only lille issue is for maven-resources-plugin-3.3.0-tests.jar that contains a unit/test-dir/resourceSystemProperties_Filtering/target/classes/file4.txt file containing current working directory (current-working-directory = D:\\Entwicklung\\Projekte\\maven-resources-plugin\\target\\checkout in the reference build) I'll open a Jira issue to try to improve that in a future release Regards, Hervé On 2022/07/23 18:08:08 Michael Osipov wrote: > Hi, > > We solved 11 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317827=12348676 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOURCES%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1789/ > https://repository.apache.org/content/repositories/maven-1789/org/apache/maven/plugins/maven-resources-plugin/3.3.0/maven-resources-plugin-3.3.0-source-release.zip > > Source release checksum(s): > maven-resources-plugin-3.3.0-source-release.zip > sha512: > c7df1d5713d08c942d2f6b3a1b3d8463e3b5ef284470bb0efc2bbb241c5f224747e43007c9af6bdef82d4e220d926dbf490a959b6c290bc9c0106db70fc74752 > > Staging site: > https://maven.apache.org/plugins-archives/maven-resources-plugin-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Site Plugin version 4.0.0-M3
+1 Reproducible Builds ok: reference done with JDK 8 on Windows Regards, Hervé On 2022/07/22 17:21:24 Michael Osipov wrote: > Hi, > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12352119 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1788/ > https://repository.apache.org/content/repositories/maven-1788/org/apache/maven/plugins/maven-site-plugin/4.0.0-M3/maven-site-plugin-4.0.0-M3-source-release.zip > > Source release checksum(s): > maven-site-plugin-4.0.0-M3-source-release.zip > sha512: > 76881569000e75679be355893a54d00f791f586637ff76f9767cb5034d184feb490b28994966d8f23deab870480868ee32e6525aa1aabd68108c047d1799d4c0 > > Staging site: > https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
