Re: Javac server?

The server makes sense when you want to have an incremental compiler. We talked about it with Robert at the ASF conference 5 years ago. If the server is tracing every change of your workspace (repo url, hash, branch) and the list of sources too, then you can speed up the compiler. T On Sun, Nov

Re: Javac server?

No experience with it but from profilings I did on maven, compilation is not that expensive compared to plugin setup in most projects so maven shell/daemon or so are likely a first step which can be more interesting in terms of overall perf (then this server can be the next step). Romain

[GitHub] [maven-doxia] dependabot[bot] closed pull request #42: Bump xmlunit-matchers from 2.7.0 to 2.8.0

dependabot[bot] closed pull request #42: URL: https://github.com/apache/maven-doxia/pull/42 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

[GitHub] [maven-doxia] dependabot[bot] opened a new pull request #44: Bump xmlunit-core from 2.7.0 to 2.8.1

dependabot[bot] opened a new pull request #44: URL: https://github.com/apache/maven-doxia/pull/44 Bumps [xmlunit-core](https://github.com/xmlunit/xmlunit) from 2.7.0 to 2.8.1. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases;>xmlunit-core's releases.

[GitHub] [maven-doxia] dependabot[bot] opened a new pull request #45: Bump xmlunit-matchers from 2.7.0 to 2.8.1

dependabot[bot] opened a new pull request #45: URL: https://github.com/apache/maven-doxia/pull/45 Bumps [xmlunit-matchers](https://github.com/xmlunit/xmlunit) from 2.7.0 to 2.8.1. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases;>xmlunit-matchers's

[GitHub] [maven-doxia] dependabot[bot] closed pull request #43: Bump xmlunit-core from 2.7.0 to 2.8.0

dependabot[bot] closed pull request #43: URL: https://github.com/apache/maven-doxia/pull/43 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

Javac server?

Hey folks, I had never heard about this javac server before https://openjdk.java.net/jeps/139 Is there any way we can exploit it in order to speed up the build? Is it enough to execute javac tool inside the same JVM of Maven core to get the same results? Do anyone have experience with it?

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Thanks and +1 Le dim. 15 nov. 2020 à 20:01, Michael Osipov a écrit : > Am 2020-11-15 um 19:51 schrieb Romain Manni-Bucau: > > Le dim. 15 nov. 2020 à 19:36, Michael Osipov a > écrit : > > > >> Am 2020-11-15 um 17:26 schrieb Romain Manni-Bucau: > >>> Do we have some links/pointers on "removing

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Am 2020-11-15 um 19:51 schrieb Romain Manni-Bucau: Le dim. 15 nov. 2020 à 19:36, Michael Osipov a écrit : Am 2020-11-15 um 17:26 schrieb Romain Manni-Bucau: Do we have some links/pointers on "removing plugins from parent pom"? Just want to ensure it does not fall in user land but something

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Le dim. 15 nov. 2020 à 19:36, Michael Osipov a écrit : > Am 2020-11-15 um 17:26 schrieb Romain Manni-Bucau: > > Do we have some links/pointers on "removing plugins from parent pom"? > Just > > want to ensure it does not fall in user land but something internal. > > There is a JIRA issue and the

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Am 2020-11-15 um 17:26 schrieb Romain Manni-Bucau: Do we have some links/pointers on "removing plugins from parent pom"? Just want to ensure it does not fall in user land but something internal. There is a JIRA issue and the section has been explicitly marked as deprecated for years.

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Am 2020-11-15 um 17:03 schrieb Hervé BOUTEMY: Le vendredi 13 novembre 2020, 19:28:20 CET Michael Osipov a écrit : Am 2020-11-13 um 19:24 schrieb Robert Scholte: Removing release profile should be combined with fail on missing/unknown profile of MNG-6012 Agreed, Karl just needs to complete his

[GitHub] [maven-site] ninj commented on a change in pull request #214: document all allowed elements inside profiles

ninj commented on a change in pull request #214: URL: https://github.com/apache/maven-site/pull/214#discussion_r523791519 ## File path: content/apt/guides/introduction/introduction-to-profiles.apt ## @@ -346,7 +346,8 @@ mvn groupId:artifactId:goal -P !profile-1,!profile-2

[GitHub] [maven-site] michael-o commented on a change in pull request #214: document all allowed elements inside profiles

michael-o commented on a change in pull request #214: URL: https://github.com/apache/maven-site/pull/214#discussion_r523790799 ## File path: content/apt/guides/introduction/introduction-to-profiles.apt ## @@ -346,7 +346,8 @@ mvn groupId:artifactId:goal -P !profile-1,!profile-2

[GitHub] [maven-site] ninj commented on a change in pull request #214: document all allowed elements inside profiles

ninj commented on a change in pull request #214: URL: https://github.com/apache/maven-site/pull/214#discussion_r523790558 ## File path: content/apt/guides/introduction/introduction-to-profiles.apt ## @@ -346,7 +346,8 @@ mvn groupId:artifactId:goal -P !profile-1,!profile-2

[GitHub] [maven-site] elharo commented on a change in pull request #214: document all allowed elements inside profiles

elharo commented on a change in pull request #214: URL: https://github.com/apache/maven-site/pull/214#discussion_r523789400 ## File path: content/apt/guides/introduction/introduction-to-profiles.apt ## @@ -346,7 +346,8 @@ mvn groupId:artifactId:goal -P !profile-1,!profile-2

[GitHub] [maven-site] ninj opened a new pull request #214: document all allowed elements inside profiles

ninj opened a new pull request #214: URL: https://github.com/apache/maven-site/pull/214 Previously the list was incomplete but did not infer the list was partial, e.g. by using the word "some". If a user comes across the introductory guide first, then it is easy to miss the complete

Re: [DISCUSS] Next release should a pre Maven 4.0.0

very good idea such an alpha will also be the opportunity to test MNG-5001 = really check @readonly Mojo parameter, with warning instead of failure, because it seems there are unexpected side effects for example on maven-site-plugin Regards, Hervé Le jeudi 12 novembre 2020, 20:00:21 CET

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Do we have some links/pointers on "removing plugins from parent pom"? Just want to ensure it does not fall in user land but something internal. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: [VOTE] Release Apache Maven JLink Plugin version 3.0.0

+1 build reproduced: JDK 8 on an Unix Regards, Hervé Le mercredi 11 novembre 2020, 23:14:35 CET Karl Heinz Marbaise a écrit : > Hi, > > We solved 37 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321432 > rsion=12343851 > > There are still a couple of issues

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Le vendredi 13 novembre 2020, 19:28:20 CET Michael Osipov a écrit : > Am 2020-11-13 um 19:24 schrieb Robert Scholte: > > Removing release profile should be combined with fail on missing/unknown > > profile of MNG-6012 > Agreed, Karl just needs to complete his implementation. > > > Remove plugin

Re: [VOTE] Release Apache Maven JLink Plugin version 3.0.0

This is +1 from me. I need more binding VOTE's of PMC's... Kind regards Karl Heinz Marbaise On 11.11.20 23:14, Karl Heinz Marbaise wrote: Hi, We solved 37 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321432=12343851 There are still a couple of issues left in