[GitHub] [maven] kwin commented on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
kwin commented on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988594671 @gnodet Indeed I couldn't find anything either yet. TBH I have just taken the information from https://books.sonatype.com/mvnref-book/reference/writing-plugins-sect-custom-plugin.html#writing-plugins-sect-failure which I consider a pretty reliable source. But maybe the different handling of those exceptions has vanished over time. Will do some more tests -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7354) Refactor MavenCli to ease extensibility
[
https://issues.apache.org/jira/browse/MNG-7354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455049#comment-17455049
]
Michael Osipov commented on MNG-7354:
-
I am excited to see what exactly needs to be done...
> Refactor MavenCli to ease extensibility
> ---
>
> Key: MNG-7354
> URL: https://issues.apache.org/jira/browse/MNG-7354
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Priority: Major
>
> {{mvnd}} has to fully rewrite {{MavenCli}} in order to extend / slightly
> alter its behavior.
> The goal is to avoid code duplication and ease maintenance for mvnd when
> upgrading maven.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven] kwin commented on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
kwin commented on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988618617 I tried it out with a dummy mojo and both exceptions behave exactly the same, i.e. both emit "BUILD FAILURE". I couldn't influence the build outcome with any of the `--fail-xxx` options nor continue the build after the exception happened. I had a quick look in the commit logs and found (https://github.com/apache/maven/commit/06dc81b54e48b76ce25675f2ae52e39ac8aeb396#diff-976d393f31905911c189adc496696a5047b0aae4526ba1c5d13bf7502ce2cbca) which once treated `MojoExecutionException` separately, but that class has been removed. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] kwin commented on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
kwin commented on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988624535 Given that, I would recommend to either reestablish the different semantics or deprecate one exception class of the two. In any case right now it is highly confusing why there are two different exception classes and when to use which in mojos. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] kwin edited a comment on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
kwin edited a comment on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988618617 I tried it out with a dummy mojo and both exceptions behave exactly the same, i.e. both emit "BUILD FAILURE". I couldn't influence the build outcome with any of the `--fail-xxx` options nor continue the build after the exception happened. I had a quick look in the commit logs and found (https://github.com/apache/maven/commit/06dc81b54e48b76ce25675f2ae52e39ac8aeb396#diff-976d393f31905911c189adc496696a5047b0aae4526ba1c5d13bf7502ce2cbca) which once treated `MojoExecutionException` separately, but that class has been removed in https://github.com/apache/maven/commit/ae1501b9f67db880ea7f16299f95f00ce04728ff -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] kwin edited a comment on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
kwin edited a comment on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988618617 I tried it out with a dummy mojo and both exceptions behave exactly the same, i.e. both emit "BUILD FAILURE". I couldn't influence the build outcome with any of the `--fail-xxx` options nor continue the build after the exception happened. I had a quick look in the commit logs and found (https://github.com/apache/maven/commit/06dc81b54e48b76ce25675f2ae52e39ac8aeb396#diff-976d393f31905911c189adc496696a5047b0aae4526ba1c5d13bf7502ce2cbca) which once treated `MojoExecutionException` separately, but that class has been removed in https://github.com/apache/maven/commit/ae1501b9f67db880ea7f16299f95f00ce04728ff (with Maven 3), so most probably having two different exception classes is no longer useful in Maven 3... -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] kwin commented on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
kwin commented on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988638938 Dug a bit deeper and found https://github.com/apache/maven/blob/ed370a6382ee4e431d36ae38454174b94d4f33aa/maven-core/src/main/java/org/apache/maven/DefaultMaven.java#L235-L255 for the different handling. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] gnodet commented on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
gnodet commented on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988654452 > Dug a bit deeper and found > > https://github.com/apache/maven/blob/ed370a6382ee4e431d36ae38454174b94d4f33aa/maven-core/src/main/java/org/apache/maven/DefaultMaven.java#L235-L255 > > for the different handling. Now, the exceptions are handled in https://github.com/apache/maven/blob/3982c195e91e3ea0f73ce9e61c6ddc57137726e9/maven-core/src/main/java/org/apache/maven/lifecycle/internal/builder/BuilderCommon.java and no case is done whether the exception is a `MojoFailureException` or `MojoExecutionException` which is coherent with your experiments. If we confirm this, I'd change the javadoc and eventually deprecate one of the exceptions. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] gnodet edited a comment on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
gnodet edited a comment on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988654452 > Dug a bit deeper and found > > https://github.com/apache/maven/blob/ed370a6382ee4e431d36ae38454174b94d4f33aa/maven-core/src/main/java/org/apache/maven/DefaultMaven.java#L235-L255 > > for the different handling. Now, the exceptions are handled in [`BuilderCommon`](https://github.com/apache/maven/blob/3982c195e91e3ea0f73ce9e61c6ddc57137726e9/maven-core/src/main/java/org/apache/maven/lifecycle/internal/builder/BuilderCommon.java) and no case is done whether the exception is a `MojoFailureException` or `MojoExecutionException` which is coherent with your experiments. If we confirm this, I'd change the javadoc and eventually deprecate one of the exceptions. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] rmannibucau commented on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
rmannibucau commented on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988675286 My understanding was that MojoExecutionException is a wrapper around another exception as primary usage whereas MojoFailureException is a root exception by itself (and previous handling tends to confirm it). Overall the need of these exception is that mojo don't throw an Exception/Throwable but there is no technical reason - in particular now, so ultimately we can just deprecate both and change mojo contract for 4.0, no? -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] kwin commented on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
kwin commented on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988694442 > Overall the need of these exception is that mojo don't throw an Exception/Throwable but there is no technical reason I think the reason is to throw an exception which would allow Maven to continue (by using `--fail-never` or `--fail-at-end`, https://maven.apache.org/ref/3.8.4/maven-embedder/cli.html). Using an unchecked exception will IMHO always lead to an immediate failure and broken Maven build. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] rmannibucau commented on pull request #632: [MNG-7351] clarify differences between MojoFailureException and MojoExecutionException in javadoc
rmannibucau commented on pull request #632: URL: https://github.com/apache/maven/pull/632#issuecomment-988696241 @kwin not sure, `--fail-never` will ignore the exception and `--fail-at-end` will stack it to fail after other modules build so MojoXXXExceptons never bring anything in this logic (as proven by BuilderCommon impl) so think it is fine to remove this constraint. There is no real recovery exception in maven - and don't think we need one. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[ https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455216#comment-17455216 ] Patrick Ruckstuhl commented on MDEP-753: Do I see this correct that the actual issue would be fixed as soon as maven-dependency-analyzer is released and then maven-dependency-plugin upgrades to that newer version? Is there anything that can be done to help getting this done? As mentioned, this basically blocks upgrading to Java 17 > Non-test dependency reported as Non-test scoped test only dependency > > > Key: MDEP-753 > URL: https://issues.apache.org/jira/browse/MDEP-753 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: analyze >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > > Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the > plugin. I'm not immediately sure whether this is a regression: > [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @ > google-http-client --- > Warning: Non-test scoped test only dependencies found: > Warning: com.google.guava:guava:jar:30.1.1-android:compile > Warning: io.opencensus:opencensus-api:jar:0.28.0:compile > Changing Guava to scope test breaks the build, which is expected based on the > code. The warning seems incorrect. > https://github.com/googleapis/google-http-java-client/pull/1396 > https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MRESOURCES-269) Symlinks cause copying resources to fail
[ https://issues.apache.org/jira/browse/MRESOURCES-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455231#comment-17455231 ] Jimisola Laursen commented on MRESOURCES-269: - [~slachiewicz] It does not work for me. With the explicit dependency on 3.3.0-SNAPSHOT Maven succeeds without errors. However, the _symbolic link_ of the file (log4j2.yml) is copied to target/classes and _not_ the actual file. The symbolic links now points to the wrong relative path and log4j2 therefore does not pick it up. Hence, I'm back to square 1. I would like for maven-resources-plugin to copy the actual file to target/classes. There seems to be inconsistency since another symbolic link that points to a directory has all its content (5-6 files) copied to target/classes. That is, actual directory structure is copied if sym link but just sym link if it is a file. Is this correct or have I missed something? > Symlinks cause copying resources to fail > > > Key: MRESOURCES-269 > URL: https://issues.apache.org/jira/browse/MRESOURCES-269 > Project: Maven Resources Plugin > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: jks >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.3.0 > > Attachments: MRESOURCES-269.tar.gz, log.txt > > > Copying a symlink fails if the target does not exist. If the symlink is > relative the order that the resources are copied matter. If A points to B > but A is copied before B the copying of A will fail with a non-helpful > message "Failed to execute goal ... on project xxx: ". > > This started failing for me on 3.2.0 (and works on 3.1.0) but that might be > because somewhere in the dependencies the traversal order changed somehow. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (MRESOURCES-237) Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior
[
https://issues.apache.org/jira/browse/MRESOURCES-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454788#comment-17454788
]
Jimisola Laursen edited comment on MRESOURCES-237 at 12/8/21, 1:22 PM:
---
[~slachiewicz] It does not work for me. With the explicit dependency on
3.3.0-SNAPSHOT Maven succeeds without errors.
However, the _symbolic link_ of the file (log4j2.yml) is copied to
target/classes and _not_ the actual file.
The symbolic links now points to the wrong relative path and log4j2 therefore
does not pick it up.
Hence, I'm back to square 1. I would like for maven-resources-plugin to copy
the actual file to target/classes.
There seems to be inconsistency since another symbolic link that points to a
directory has all its content (5-6 files) copied to target/classes.
That is, actual directory structure is copied if sym link but just sym link if
it is a file. Is this correct or have I missed something?
was (Author: JIRAUSER281352):
[~slachiewicz] It does not work me. With the explicit dependcy on
3.3.0-SNAPSHOT Maven succeeds without errors.
However, the symbolic link of the file is copied to target/classes and not the
actual file. I'm back to square 1. I would like for maven-resources-plugin to
copy the actual file to target/classes.
There seems to be inconsistency as another symbolic links pointer to a
directory has all its content (5-6 files) copied to target/classes.
> Resource plugin's handling of symbolic links changed in 3.0.x, broke existing
> behavior
> --
>
> Key: MRESOURCES-237
> URL: https://issues.apache.org/jira/browse/MRESOURCES-237
> Project: Maven Resources Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.1.0, 3.2.0
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00)
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-200.fc25.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Brian D. Johnson
>Assignee: Olivier Lamy
>Priority: Minor
> Fix For: 3.3.0
>
> Attachments: a.tgz
>
>
> It looks like the handling of symbolic links in the
> {{maven-resources-plugin}} has changed in version 3.0.x. I'm submitting a
> JIRA because it breaks the previous behavior and I have not been able to find
> this documented anywhere as an intended change.
> *Use case:* Multi-module maven project. We have a custom log4j2
> configuration file we use during testing. Instead of maintaining this file
> in multiple {{src/test/resources}} directories, we instead maintain a single
> copy of the file at the project's root level and create symbolic links from
> each module's {{src/test/resources}} directory to the file using relative
> paths.
> *2.7 Behavior:* the symlink was evaluated and the target file was copied to
> {{target/test-classes/}}.
> *3.0.x Behavior:* the symlink is copied to {{target/test-classes/}} verbatim.
> The symlink's relative path results in the symlink pointing to the wrong
> file location. The log4j2 configuration is not found.
> *Requested Change:* Either revert to the original 2.7 behavior, or document
> the change and provide a configuration parameter to allow the legacy behavior.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MWRAPPER-29) Project should build successfully with verify goal
[
https://issues.apache.org/jira/browse/MWRAPPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455301#comment-17455301
]
Slawomir Jaranowski commented on MWRAPPER-29:
-
PR: https://github.com/apache/maven-wrapper/pull/1
> Project should build successfully with verify goal
> --
>
> Key: MWRAPPER-29
> URL: https://issues.apache.org/jira/browse/MWRAPPER-29
> Project: Maven Wrapper
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> Project should build successfully with
> {code}
> mvn verify -P run-its
> {code}
> During IT tests we should use current build artifacts not existed from local
> maven repo
> reproduce - clen local repo
> {code}
> rm -rf ~/.m2/repository/org/apache/maven/wrapper/
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MWRAPPER-30) Add help mojo
[
https://issues.apache.org/jira/browse/MWRAPPER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455305#comment-17455305
]
Slawomir Jaranowski commented on MWRAPPER-30:
-
PR: https://github.com/apache/maven-wrapper/pull/2
> Add help mojo
> -
>
> Key: MWRAPPER-30
> URL: https://issues.apache.org/jira/browse/MWRAPPER-30
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> {{help mojo}} is useful to check available params and simple plugin
> documentation
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-enforcer] dependabot[bot] opened a new pull request #129: Bump mrm-maven-plugin from 1.2.0 to 1.3.0
dependabot[bot] opened a new pull request #129: URL: https://github.com/apache/maven-enforcer/pull/129 Bumps [mrm-maven-plugin](https://github.com/mojohaus/mrm) from 1.2.0 to 1.3.0. Release notes Sourced from https://github.com/mojohaus/mrm/releases";>mrm-maven-plugin's releases. 1.3.0 making timestamp deserialization consistent (https://github-redirect.dependabot.com/mojohaus/mrm/issues/18";>#18) https://github.com/or-shachar";>@or-shachar 🚀 New features and improvements Upgrade to Jetty 9.4.43.v20210629 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/35";>#35) https://github.com/olamy";>@olamy java 1.8 mandatory amd some codebase update (https://github-redirect.dependabot.com/mojohaus/mrm/issues/33";>#33) https://github.com/olamy";>@olamy switch to github actions, add dependabot and use release drafter (https://github-redirect.dependabot.com/mojohaus/mrm/issues/26";>#26) https://github.com/olamy";>@olamy 📦 Dependency updates Bump mockito-core from 3.12.4 to 4.1.0 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/62";>#62) https://github.com/dependabot";>@dependabot Bump mojo-parent from 63 to 65 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/63";>#63) https://github.com/dependabot";>@dependabot Bump plexus-archiver from 4.2.5 to 4.2.6 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/60";>#60) https://github.com/dependabot";>@dependabot Bump actions/checkout from 2.3.5 to 2.4.0 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/59";>#59) https://github.com/dependabot";>@dependabot Bump actions/checkout from 2.3.4 to 2.3.5 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/58";>#58) https://github.com/dependabot";>@dependabot Bump actions/setup-java from 2.3.0 to 2.3.1 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/54";>#54) https://github.com/dependabot";>@dependabot Bump maven-war-plugin from 3.3.1 to 3.3.2 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/53";>#53) https://github.com/dependabot";>@dependabot Bump plexus-utils from 3.4.0 to 3.4.1 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/52";>#52) https://github.com/dependabot";>@dependabot Bump mockito-core from 3.12.3 to 3.12.4 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/51";>#51) https://github.com/dependabot";>@dependabot Bump mockito-core from 3.12.1 to 3.12.3 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/50";>#50) https://github.com/dependabot";>@dependabot Bump actions/setup-java from 2.2.0 to 2.3.0 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/49";>#49) https://github.com/dependabot";>@dependabot Bump mockito-core from 3.11.2 to 3.12.1 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/48";>#48) https://github.com/dependabot";>@dependabot Bump commons-io from 2.7 to 2.11.0 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/46";>#46) https://github.com/dependabot";>@dependabot Bump mockito-core from 1.9.0 to 3.11.2 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/27";>#27) https://github.com/dependabot";>@dependabot Bump plexus-archiver from 3.4 to 4.2.5 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/36";>#36) https://github.com/dependabot";>@dependabot Bump junit from 4.13.1 to 4.13.2 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/42";>#42) https://github.com/dependabot";>@dependabot Bump maven-enforcer-plugin from 3.0.0-M1 to 3.0.0 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/41";>#41) https://github.com/dependabot";>@dependabot Bump maven-common-artifact-filters from 1.4 to 3.2.0 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/37";>#37) https://github.com/dependabot";>@dependabot Bump maven-war-plugin from 3.2.1 to 3.3.1 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/38";>#38) https://github.com/dependabot";>@dependabot Bump commons-io from 2.0.1 to 2.11.0 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/32";>#32) https://github.com/dependabot";>@dependabot Bump actions/setup-java from 2.1.0 to 2.2.0 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/31";>#31) https://github.com/dependabot";>@dependabot Bump jetty-maven-plugin from 8.0.1.v20110908 to 8.1.16.v20140903 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/29";>#29) https://github.com/dependabot";>@dependabot Bump mojo-parent from 50 to 63 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/30";>#30) https://github.com/dependabot";>@dependabot Bump junit from 4.10 to 4.13.1 (https://github-redirect.dependabot.com/mojohaus/mrm/issues/24";>#24) https://github.com/dependabot";>@dependabot Commits https://github.com/mojohaus/mrm/commit/1a34933383abe618c61914614e1febbae3942063";>1a34933 [maven-
[jira] [Updated] (MWRAPPER-29) Project should build successfully with verify lifecycle
[
https://issues.apache.org/jira/browse/MWRAPPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MWRAPPER-29:
Summary: Project should build successfully with verify lifecycle (was:
Project should build successfully with verify goal)
> Project should build successfully with verify lifecycle
> ---
>
> Key: MWRAPPER-29
> URL: https://issues.apache.org/jira/browse/MWRAPPER-29
> Project: Maven Wrapper
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> Project should build successfully with
> {code}
> mvn verify -P run-its
> {code}
> During IT tests we should use current build artifacts not existed from local
> maven repo
> reproduce - clen local repo
> {code}
> rm -rf ~/.m2/repository/org/apache/maven/wrapper/
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-filtering] dependabot[bot] opened a new pull request #25: Bump plexus-utils from 3.3.0 to 3.4.1
dependabot[bot] opened a new pull request #25: URL: https://github.com/apache/maven-filtering/pull/25 Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from 3.3.0 to 3.4.1. Release notes Sourced from https://github.com/codehaus-plexus/plexus-utils/releases";>plexus-utils's releases. 3.4.1 🐛 Bug Fixes Fixes https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/163";>#163: Regression: encoding error when parsing a ISO-8859-1 xml (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/164";>#164) https://github.com/belingueres";>@belingueres 📦 Dependency updates Bump actions/setup-java from 2.2.0 to 2.3.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/168";>#168) https://github.com/dependabot";>@dependabot Bump jmh-generator-annprocess from 1.32 to 1.33 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/166";>#166) https://github.com/dependabot";>@dependabot Bump jmh-core from 1.32 to 1.33 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/165";>#165) https://github.com/dependabot";>@dependabot Bump actions/setup-java from 2.1.0 to 2.2.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/167";>#167) https://github.com/dependabot";>@dependabot Bump junit from 4.13.1 to 4.13.2 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/162";>#162) https://github.com/dependabot";>@dependabot Bump actions/setup-java from 1 to 2.1.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/157";>#157) https://github.com/dependabot";>@dependabot Bump jmh-generator-annprocess from 1.29 to 1.32 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/159";>#159) https://github.com/dependabot";>@dependabot Bump jmh-core from 1.29 to 1.32 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/160";>#160) https://github.com/dependabot";>@dependabot Bump actions/cache from 2.1.5 to 2.1.6 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/161";>#161) https://github.com/dependabot";>@dependabot Bump actions/checkout from 2 to 2.3.4 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/154";>#154) https://github.com/dependabot";>@dependabot 3.4.0 Enforcing JDK 11 on release (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/148";>#148) https://github.com/mkarg";>@mkarg Using JDK 16 GA instead of JDK 16 EA (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/147";>#147) https://github.com/mkarg";>@mkarg Fixed infinite loop in MXParser and reactivate tests in MXParserTest (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/119";>#119,https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/118";>#118) https://github.com/belingueres";>@belingueres Added support for PPC64LE (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/97";>#97) https://github.com/ezeeyahoo";>@ezeeyahoo Avoid build issues with symlink (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/90";>#90) https://github.com/olamy";>@olamy New feature FileUtils.linkFile(source, destination) (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/82";>#82) https://github.com/mkarg";>@mkarg Fix Javadoc build with Java 11 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/88";>#88) https://github.com/olamy";>@olamy Support combine.keys (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/76";>#76) https://github.com/rfscholte";>@rfscholte Support combine.self="remove" (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/75";>#75,https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/74";>#74) https://github.com/belingueres";>@belingueres Input location (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/62";>#62,https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/61";>#61) https://github.com/hboutemy";>@hboutemy UT improvement : Check that symlinks resources are preserved during git clone (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/56";>#56) https://github.com/rfscholte";>@rfscholte Junit4 annotations (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/55";>#55) https://github.com/rfscholte";>@rfscholte Test failure in CommandlineTest#testExecuteBinaryOnPath with Maven 3.5.4 or later (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/50";>#50) https://github.com/belingueres";>@belingueres PrettyPrintXMLWriter fails with a java.util.N
[GitHub] [maven-wrapper] hboutemy merged pull request #1: [MWRAPPER-29] Possibility to build project by verify lifecycle
hboutemy merged pull request #1: URL: https://github.com/apache/maven-wrapper/pull/1 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-wrapper] hboutemy commented on pull request #1: [MWRAPPER-29] Possibility to build project by verify lifecycle
hboutemy commented on pull request #1: URL: https://github.com/apache/maven-wrapper/pull/1#issuecomment-989029965 nice fix: thanks a lot -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-wrapper] hboutemy merged pull request #2: [MWRAPPER-30] Add help mojo
hboutemy merged pull request #2: URL: https://github.com/apache/maven-wrapper/pull/2 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MWRAPPER-29) Project should build successfully with verify lifecycle
[
https://issues.apache.org/jira/browse/MWRAPPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MWRAPPER-29.
-
Fix Version/s: 3.1.0
Assignee: Herve Boutemy
Resolution: Fixed
merged in
https://github.com/apache/maven-wrapper/commit/62c6a95364ea44243b6c30a17ee793fce067a4c2
thank you
> Project should build successfully with verify lifecycle
> ---
>
> Key: MWRAPPER-29
> URL: https://issues.apache.org/jira/browse/MWRAPPER-29
> Project: Maven Wrapper
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.1.0
>
>
> Project should build successfully with
> {code}
> mvn verify -P run-its
> {code}
> During IT tests we should use current build artifacts not existed from local
> maven repo
> reproduce - clen local repo
> {code}
> rm -rf ~/.m2/repository/org/apache/maven/wrapper/
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MWRAPPER-30) Add help mojo
[
https://issues.apache.org/jira/browse/MWRAPPER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-30:
--
Priority: Minor (was: Major)
> Add help mojo
> -
>
> Key: MWRAPPER-30
> URL: https://issues.apache.org/jira/browse/MWRAPPER-30
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Slawomir Jaranowski
>Assignee: Herve Boutemy
>Priority: Minor
> Fix For: 3.1.0
>
>
> {{help mojo}} is useful to check available params and simple plugin
> documentation
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (MWRAPPER-30) Add help mojo
[
https://issues.apache.org/jira/browse/MWRAPPER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MWRAPPER-30.
-
Fix Version/s: 3.1.0
Assignee: Herve Boutemy
Resolution: Fixed
merged in
https://github.com/apache/maven-wrapper/commit/5a307fd47ffb7b26253b837d613fa9375626d851
nice improvement, thank you
> Add help mojo
> -
>
> Key: MWRAPPER-30
> URL: https://issues.apache.org/jira/browse/MWRAPPER-30
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Slawomir Jaranowski
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.1.0
>
>
> {{help mojo}} is useful to check available params and simple plugin
> documentation
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MWRAPPER-24) mvnw calls which(1) which is an external command
[ https://issues.apache.org/jira/browse/MWRAPPER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MWRAPPER-24: -- Priority: Minor (was: Major) > mvnw calls which(1) which is an external command > > > Key: MWRAPPER-24 > URL: https://issues.apache.org/jira/browse/MWRAPPER-24 > Project: Maven Wrapper > Issue Type: Improvement > Components: Maven Wrapper Scripts >Affects Versions: 0.5.6 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Minor > Fix For: 3.1.0 > > > see MNG-7270 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MWRAPPER-27) rework mvnw* scripts to better match mvn* from Maven 3.8
[ https://issues.apache.org/jira/browse/MWRAPPER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MWRAPPER-27: -- Priority: Minor (was: Major) > rework mvnw* scripts to better match mvn* from Maven 3.8 > > > Key: MWRAPPER-27 > URL: https://issues.apache.org/jira/browse/MWRAPPER-27 > Project: Maven Wrapper > Issue Type: Improvement > Components: Maven Wrapper Scripts >Affects Versions: 0.5.6 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Minor > Fix For: 3.1.0 > > > there has been much improvement done in recent Maven versions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MWRAPPER-25) fix installer messages
[
https://issues.apache.org/jira/browse/MWRAPPER-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-25:
--
Priority: Minor (was: Major)
> fix installer messages
> --
>
> Key: MWRAPPER-25
> URL: https://issues.apache.org/jira/browse/MWRAPPER-25
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Jar
>Affects Versions: 0.5.6
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Minor
> Fix For: 3.1.0
>
>
> {noformat}$ MVNW_VERBOSE=true ./mvnw -v
> Found .mvn/wrapper/maven-wrapper.jar
> /home/herve/projets/maven/sources/core/maven-wrapper
> Apache Maven Wrapper 3.0.3-SNAPSHOT
> Downloading Maven binary from
> https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.8.3/apache-maven-3.8.3-bin.zip
> Exception in thread "main" java.lang.RuntimeException: Maven distribution
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.8.3/apache-maven-3.8.3-bin.zip'
> contains too many directories. Expected to find exactly 1 directory.
> at org.apache.maven.wrapper.Installer.createDist(Installer.java:113)
> at
> org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:160)
> at
> org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:69)
> {noformat}
> 2 issues:
> 1. "Downloading Maven binary from ..." when we're not at download but
> installing to local directory
> 2. "RuntimeException: Maven distribution
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.8.3/apache-maven-3.8.3-bin.zip'
> contains too many directories": it's not about download url but local
> installation directory
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-wrapper] slawekjaranowski commented on pull request #1: [MWRAPPER-29] Possibility to build project by verify lifecycle
slawekjaranowski commented on pull request #1: URL: https://github.com/apache/maven-wrapper/pull/1#issuecomment-989039486 your welcome -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MWRAPPER-31) Get rid of maven-artifact-transfer
Slawomir Jaranowski created MWRAPPER-31:
---
Summary: Get rid of maven-artifact-transfer
Key: MWRAPPER-31
URL: https://issues.apache.org/jira/browse/MWRAPPER-31
Project: Maven Wrapper
Issue Type: Improvement
Components: Maven Wrapper Plugin
Reporter: Slawomir Jaranowski
According to
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=155749857
{{maven-artifact-transfer}} should be not used for plugins with maven 3.1.x api
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MWRAPPER-31) Get rid of maven-artifact-transfer
[
https://issues.apache.org/jira/browse/MWRAPPER-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455924#comment-17455924
]
Slawomir Jaranowski commented on MWRAPPER-31:
-
I will do it.
> Get rid of maven-artifact-transfer
> --
>
> Key: MWRAPPER-31
> URL: https://issues.apache.org/jira/browse/MWRAPPER-31
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> According to
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=155749857
> {{maven-artifact-transfer}} should be not used for plugins with maven 3.1.x
> api
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (MSITE-876) Execution default-deploy of goal ...deploy failed: An API incompatibility was encountered while executing ....deploy: java.lang.NoSuchMethodError: org.apache.maven.wagon.
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MSITE-876:
Assignee: (was: Michael Osipov)
> Execution default-deploy of goal ...deploy failed: An API incompatibility was
> encountered while executing deploy: java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> --
>
> Key: MSITE-876
> URL: https://issues.apache.org/jira/browse/MSITE-876
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.9.1
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.10.0
>
>
> When using maven-site-plugin 3.9.1 with the additional plugin dependency
> {{org.apache.maven.wagon:wagon-webdav-jackrabbit:3.3.1}} I experience the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy (default-deploy) on
> project ...: Execution default-deploy of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy:
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/plugins/maven-site-plugin/3.9.1/maven-site-plugin-3.9.1.jar
> [ERROR] urls[1] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-webdav-jackrabbit/3.3.1/wagon-webdav-jackrabbit-3.3.1.jar
> [ERROR] urls[2] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-http-shared/3.3.1/wagon-http-shared-3.3.1.jar
> [ERROR] urls[3] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar
> [ERROR] urls[4] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/jackrabbit/jackrabbit-webdav/2.14.4/jackrabbit-webdav-2.14.4.jar
> [ERROR] urls[5] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/commons-codec/commons-codec/1.10/commons-codec-1.10.jar
> [ERROR] urls[6] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/slf4j/jcl-over-slf4j/1.7.25/jcl-over-slf4j-1.7.25.jar
> [ERROR] urls[7] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpclient/4.5.6/httpclient-4.5.6.jar
> [ERROR] urls[8] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpcore/4.4.10/httpcore-4.4.10.jar
> [ERROR] urls[9] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-exec/1.5.1/maven-reporting-exec-1.5.1.jar
> [ERROR] urls[11] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[12] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> [ERROR] urls[13] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
> [ERROR] urls[14] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[15] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar
> [ERROR] urls[16] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[17] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[18] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/maven-archiver/3.5.0/maven-archiver-3.5.0.jar
> [ERROR] urls[19] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatyp
[jira] [Updated] (MSITE-876) Execution default-deploy of goal ...deploy failed: An API incompatibility was encountered while executing ....deploy: java.lang.NoSuchMethodError: org.apache.maven.wagon.s
[
https://issues.apache.org/jira/browse/MSITE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-876:
-
Fix Version/s: (was: 3.10.0)
> Execution default-deploy of goal ...deploy failed: An API incompatibility was
> encountered while executing deploy: java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> --
>
> Key: MSITE-876
> URL: https://issues.apache.org/jira/browse/MSITE-876
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.9.1
>Reporter: Konrad Windszus
>Priority: Major
>
> When using maven-site-plugin 3.9.1 with the additional plugin dependency
> {{org.apache.maven.wagon:wagon-webdav-jackrabbit:3.3.1}} I experience the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy (default-deploy) on
> project ...: Execution default-deploy of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.1:deploy:
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/plugins/maven-site-plugin/3.9.1/maven-site-plugin-3.9.1.jar
> [ERROR] urls[1] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-webdav-jackrabbit/3.3.1/wagon-webdav-jackrabbit-3.3.1.jar
> [ERROR] urls[2] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/wagon/wagon-http-shared/3.3.1/wagon-http-shared-3.3.1.jar
> [ERROR] urls[3] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar
> [ERROR] urls[4] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/jackrabbit/jackrabbit-webdav/2.14.4/jackrabbit-webdav-2.14.4.jar
> [ERROR] urls[5] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/commons-codec/commons-codec/1.10/commons-codec-1.10.jar
> [ERROR] urls[6] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/slf4j/jcl-over-slf4j/1.7.25/jcl-over-slf4j-1.7.25.jar
> [ERROR] urls[7] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpclient/4.5.6/httpclient-4.5.6.jar
> [ERROR] urls[8] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/httpcomponents/httpcore/4.4.10/httpcore-4.4.10.jar
> [ERROR] urls[9] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/reporting/maven-reporting-exec/1.5.1/maven-reporting-exec-1.5.1.jar
> [ERROR] urls[11] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[12] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> [ERROR] urls[13] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
> [ERROR] urls[14] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[15] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar
> [ERROR] urls[16] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[17] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[18] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/apache/maven/maven-archiver/3.5.0/maven-archiver-3.5.0.jar
> [ERROR] urls[19] =
> file:/var/lib/jenkins/workspace/CQServer-CI_develop/.repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-
[jira] [Created] (MWRAPPER-32) Use Maven core component in provided scope
Slawomir Jaranowski created MWRAPPER-32:
---
Summary: Use Maven core component in provided scope
Key: MWRAPPER-32
URL: https://issues.apache.org/jira/browse/MWRAPPER-32
Project: Maven Wrapper
Issue Type: Improvement
Reporter: Slawomir Jaranowski
First dependency on {{maven-artifact-transfer}} should be removed because has
many transitive dependency in compile scope to Maven core artifacts.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (MWRAPPER-33) Use java 8 in maven-wrapper
Slawomir Jaranowski created MWRAPPER-33:
---
Summary: Use java 8 in maven-wrapper
Key: MWRAPPER-33
URL: https://issues.apache.org/jira/browse/MWRAPPER-33
Project: Maven Wrapper
Issue Type: Improvement
Components: Maven Wrapper Jar
Reporter: Slawomir Jaranowski
Currently {{maven-wrapper}} use java *5*.
It blocks build project on java > 8.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-wagon] hiljusti commented on pull request #72: [MNG-6975] Wagon-HTTP, set content-type when determinable from file extension
hiljusti commented on pull request #72: URL: https://github.com/apache/maven-wagon/pull/72#issuecomment-989117811 As a note: My (minor) issue could have benefited from this: https://issues.apache.org/jira/browse/MDEPLOY-289 The summary is a custom maven repository proxy, where it would be nice to not default/guess content type. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-wagon] hiljusti edited a comment on pull request #72: [MNG-6975] Wagon-HTTP, set content-type when determinable from file extension
hiljusti edited a comment on pull request #72: URL: https://github.com/apache/maven-wagon/pull/72#issuecomment-989117811 As a note: My (minor) issue could have benefited from this: https://issues.apache.org/jira/browse/MDEPLOY-289 The summary is our enterprise (amazon) used custom maven repository proxies. It would be nice to not default/guess content type when missing. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MWRAPPER-32) Use Maven core component in provided scope
[
https://issues.apache.org/jira/browse/MWRAPPER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MWRAPPER-32:
Component/s: Maven Wrapper Plugin
> Use Maven core component in provided scope
> --
>
> Key: MWRAPPER-32
> URL: https://issues.apache.org/jira/browse/MWRAPPER-32
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> First dependency on {{maven-artifact-transfer}} should be removed because has
> many transitive dependency in compile scope to Maven core artifacts.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MWRAPPER-33) Use java 8 in maven-wrapper
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MWRAPPER-33:
Description:
Currently {{maven-wrapper}} use java {*}5{*}.
It blocks build project on java > 8.
{{maven-wrapper-plugin}} require java 8, so we can use {{maven-wrapper}} with
java 5 but we can't install it.
was:
Currently {{maven-wrapper}} use java *5*.
It blocks build project on java > 8.
> Use java 8 in maven-wrapper
> ---
>
> Key: MWRAPPER-33
> URL: https://issues.apache.org/jira/browse/MWRAPPER-33
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Jar
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> Currently {{maven-wrapper}} use java {*}5{*}.
> It blocks build project on java > 8.
> {{maven-wrapper-plugin}} require java 8, so we can use {{maven-wrapper}} with
> java 5 but we can't install it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-wrapper] slachiewicz merged pull request #3: (doc) fix jenkins url
slachiewicz merged pull request #3: URL: https://github.com/apache/maven-wrapper/pull/3 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MWRAPPER-33) Use java 8 in maven-wrapper
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-33:
--
Affects Version/s: 3.1.0
> Use java 8 in maven-wrapper
> ---
>
> Key: MWRAPPER-33
> URL: https://issues.apache.org/jira/browse/MWRAPPER-33
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Jar
>Affects Versions: 3.1.0
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.2.0
>
>
> Currently {{maven-wrapper}} use java {*}5{*}.
> It blocks build project on java > 8.
> {{maven-wrapper-plugin}} require java 8, so we can use {{maven-wrapper}} with
> java 5 but we can't install it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MWRAPPER-33) Use java 8 in maven-wrapper
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-33:
--
Fix Version/s: 3.2.0
> Use java 8 in maven-wrapper
> ---
>
> Key: MWRAPPER-33
> URL: https://issues.apache.org/jira/browse/MWRAPPER-33
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Jar
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.2.0
>
>
> Currently {{maven-wrapper}} use java {*}5{*}.
> It blocks build project on java > 8.
> {{maven-wrapper-plugin}} require java 8, so we can use {{maven-wrapper}} with
> java 5 but we can't install it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MWRAPPER-33) Use java 8 in maven-wrapper
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455993#comment-17455993
]
Herve Boutemy commented on MWRAPPER-33:
---
I'll do a first step with plugin in Java 7 and wrapper in Java 6 or 7: this
will provide a smooth evolution for users
> Use java 8 in maven-wrapper
> ---
>
> Key: MWRAPPER-33
> URL: https://issues.apache.org/jira/browse/MWRAPPER-33
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Jar
>Affects Versions: 3.1.0
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.2.0
>
>
> Currently {{maven-wrapper}} use java {*}5{*}.
> It blocks build project on java > 8.
> {{maven-wrapper-plugin}} require java 8, so we can use {{maven-wrapper}} with
> java 5 but we can't install it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (MWRAPPER-34) use Java 7 for maven-wrapper-plugin and maven-wrapper.jar
Herve Boutemy created MWRAPPER-34: - Summary: use Java 7 for maven-wrapper-plugin and maven-wrapper.jar Key: MWRAPPER-34 URL: https://issues.apache.org/jira/browse/MWRAPPER-34 Project: Maven Wrapper Issue Type: Task Components: Maven Wrapper Jar, Maven Wrapper Plugin Reporter: Herve Boutemy Fix For: 3.1.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven] AlexanderAshitkin commented on a change in pull request #631: [MNG-7129] Maven cache docs updates
AlexanderAshitkin commented on a change in pull request #631: URL: https://github.com/apache/maven/pull/631#discussion_r765269522 ## File path: maven-caching-extension/src/site/markdown/GETTING-STARTED.md ## @@ -0,0 +1,69 @@ + + +## Getting Started + +To on-board incremental Maven you need to complete several steps: + +* Declare caching extension in your project +* Add cache config in `.mvn` (optional) to customize default behavior +* Validate build results and iteratively adjust config to properly reflect project specifics +* Setup remote cache (optional) + +### Declaring cache extension + +```xml + +org.apache.maven.caching +maven-caching-extension +1.0.0-SNAPSHOT + +``` + +### Adding cache config + +Copy [default config `maven-cache-config.xml`](maven-cache-config.xml) +to [`.mvn/`](https://maven.apache.org/configure.html) directory of your project. +To get overall understanding of cache machinery it is recommended to review the config and read comments. In typical +scenario you need to adjust: + +* Exclusions for unstable, temporary files or environment specific files +* Plugins reconciliation rules – add critical plugins parameters to reconciliation +* Source code files selectors. Though source code locations discovered automatically from project and plugins config, + there might be edge cases. +* remote cache location (if remote cache is used) + +### Adjusting cache config + +Having extension run usual command, like `mvn package`. Verify the caching engine is activated: + +* Check log output - there should be cache related output or initialization error message. +* Navigate to your local repo directory - there should be a sibling directory `cache` next to the usual + local `repository`. +* Find `buildinfo.xml` in the cache repository for typical module and review it. Ensure that + * expected source code files are present in the build info + * all critical plugins and their critical parameters are covered by config + +It is recommended to find the best working trade-off between fairness and cache efficiency. Adding unnecessary rules and +checks could reduce both performance and cache efficiency (hit rate). + +### Adding caching CI and remote cache + +To leverage remote cache feature there should a shared storage provide. Any technology supported +by [Maven Wagon](https://maven.apache.org/wagon/) will suffice. In simplest form it could be a http web server which +supports get/put operations ([Nginx OSS](http://nginx.org/en/) with fs module or any other equivalent). +See [Remote cache setup](CACHE-REMOTE.md) for detailed description of cache setup Review comment: fixed -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MWRAPPER-33) Use java 8 in maven-wrapper
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456017#comment-17456017
]
Slawomir Jaranowski commented on MWRAPPER-33:
-
I'm not sure if support for java < 8 is really needed.
Many Maven plugins are switched to java 8, so release with old java support is
step revert.
If somebody really need java < 8 should use old version of wrapper.
It is only my opinion.
> Use java 8 in maven-wrapper
> ---
>
> Key: MWRAPPER-33
> URL: https://issues.apache.org/jira/browse/MWRAPPER-33
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Jar
>Affects Versions: 3.1.0
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.2.0
>
>
> Currently {{maven-wrapper}} use java {*}5{*}.
> It blocks build project on java > 8.
> {{maven-wrapper-plugin}} require java 8, so we can use {{maven-wrapper}} with
> java 5 but we can't install it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven] AlexanderAshitkin opened a new pull request #633: [MNG-7129] Files selectors rework draft
AlexanderAshitkin opened a new pull request #633:
URL: https://github.com/apache/maven/pull/633
The idea is to replace glob section with glob/pattern based includes
excludes to form determenistic files set.
Current implementtation with glob might be not flexible and expressive
enough. Proposed configuration:
```xml
*.{java,properties}
/home/*/*
(cat|dog)-[0-3][0-5][0-9]\.xml
*.{iml,log}
(cat|dog)-[0-3][0-5][0-9]\.xml
```
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MNG) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [ ] Each commit in the pull request should have a meaningful subject line
and body.
- [ ] Format the pull request title like `[MNG-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MNG-XXX` with the appropriate JIRA issue. Best
practice
is to use the JIRA issue title in the pull request title and in the
first line of the
commit message.
- [ ] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [ ] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [ ] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [ ] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
[core-its]: https://maven.apache.org/core-its/core-it-suite/
--
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: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-wrapper] slachiewicz merged pull request #4: fix configuration for Maven 3.2.x
slachiewicz merged pull request #4: URL: https://github.com/apache/maven-wrapper/pull/4 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (MSHARED-687) Programmatic read-only access to Color API
[
https://issues.apache.org/jira/browse/MSHARED-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MSHARED-687:
Assignee: (was: Guillaume Boué)
> Programmatic read-only access to Color API
> --
>
> Key: MSHARED-687
> URL: https://issues.apache.org/jira/browse/MSHARED-687
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-shared-utils
>Affects Versions: maven-shared-utils-3.2.1
>Reporter: Guillaume Boué
>Priority: Minor
>
> We should provide a way to access programmatically the Color API, without
> being JAnsi specific. Read-only should suffice for now, as the styles can be
> changed through system properties. This would allow tools, like the Help
> Plugin, to interact with it without depending on the implementation.
> - Refactor JAnsi specific code currently in {{Style}} into
> {{AnsiMessageBuilder}}.
> - Make {{Style}} part of public API, and add getters {{boolean isBold()}},
> {{boolean isBright()}}, {{String getColor()}}, {{boolean isBgBright()}} and
> {{String getBgColor()}}.
> - Document {{Style.toString()}} to return a comma-separated list of the
> style components (e.g. {{bold,red}}).
> - Add a public {{List getAvailableColorNames()}} method to
> {{MessageUtils}}. Today, it would return the list of color names in the enum
> {{Ansi.Color}} if JAnsi is present, otherwise an empty list.
> With those changes, a consumer could for example do:
> {code:java}
> MessageUtils.buffer().success( Style.SUCCESS.toString() )
> {code}
> in order to print the String representation of success with its own style,
> while not depending on JAnsi.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-dependency-plugin] slachiewicz closed pull request #176: Bump doxiaVersion from 1.10 to 1.11.1
slachiewicz closed pull request #176: URL: https://github.com/apache/maven-dependency-plugin/pull/176 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-plugin] dependabot[bot] commented on pull request #176: Bump doxiaVersion from 1.10 to 1.11.1
dependabot[bot] commented on pull request #176: URL: https://github.com/apache/maven-dependency-plugin/pull/176#issuecomment-989426323 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-compiler-plugin] slachiewicz merged pull request #77: Bump qdox from 2.0.0 to 2.0.1
slachiewicz merged pull request #77: URL: https://github.com/apache/maven-compiler-plugin/pull/77 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-compiler-plugin] slachiewicz merged pull request #71: Bump mockito-core from 2.28.2 to 4.0.0
slachiewicz merged pull request #71: URL: https://github.com/apache/maven-compiler-plugin/pull/71 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-compiler-plugin] slachiewicz merged pull request #70: Bump plexusCompilerVersion from 2.8.8 to 2.9.0
slachiewicz merged pull request #70: URL: https://github.com/apache/maven-compiler-plugin/pull/70 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-compiler-plugin] dependabot[bot] commented on pull request #78: Bump mavenVersion from 3.0 to 3.8.4
dependabot[bot] commented on pull request #78: URL: https://github.com/apache/maven-compiler-plugin/pull/78#issuecomment-989429266 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-compiler-plugin] slachiewicz closed pull request #78: Bump mavenVersion from 3.0 to 3.8.4
slachiewicz closed pull request #78: URL: https://github.com/apache/maven-compiler-plugin/pull/78 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MWRAPPER-33) Use java 8 in maven-wrapper
[
https://issues.apache.org/jira/browse/MWRAPPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456182#comment-17456182
]
Herve Boutemy commented on MWRAPPER-33:
---
I'm not a fan of forcing people to upgrade if not upgrading does not cost us
anything/much (and I'm not judging "you are obsolete" people who can't upgrade)
I understand that remaining at Java 5 cost a real limitation in what JDK we can
use to build
With Java 7, we target Maven 3.3.1 https://maven.apache.org/docs/history.html
Java 6 does not add much value to the target Maven releases
Java 5 is beyond the JDK minimum acceptable version as of 2021
then MWRAPPER-34 with target JDK 7 is IMHO a good compromise to smoothly switch
to Apache Maven Wrapper: we'll see later to upgrade, there is not so much code
in wrapper to maintain
> Use java 8 in maven-wrapper
> ---
>
> Key: MWRAPPER-33
> URL: https://issues.apache.org/jira/browse/MWRAPPER-33
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Jar
>Affects Versions: 3.1.0
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.2.0
>
>
> Currently {{maven-wrapper}} use java {*}5{*}.
> It blocks build project on java > 8.
> {{maven-wrapper-plugin}} require java 8, so we can use {{maven-wrapper}} with
> java 5 but we can't install it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven] michael-o commented on pull request #631: [MNG-7129] Maven cache docs updates
michael-o commented on pull request #631: URL: https://github.com/apache/maven/pull/631#issuecomment-989575866 > All lower: https://github.com/apache/maven-site/tree/master/content/markdown I don't know where you have the uppercase convention from, but as far as I know this applies only to README, LICENSE, NOTICE, etc. That's it. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MWRAPPER-34) use Java 7 for maven-wrapper-plugin and maven-wrapper.jar
[ https://issues.apache.org/jira/browse/MWRAPPER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MWRAPPER-34: -- Description: consistent with Maven 3.3.1+ https://maven.apache.org/docs/history.html Java 7 is EOL'ed since July 2021 https://javaalmanac.io/jdk/ : that's not that far away, hellping a little bit people stuck here does not cost us so much > use Java 7 for maven-wrapper-plugin and maven-wrapper.jar > - > > Key: MWRAPPER-34 > URL: https://issues.apache.org/jira/browse/MWRAPPER-34 > Project: Maven Wrapper > Issue Type: Task > Components: Maven Wrapper Jar, Maven Wrapper Plugin >Reporter: Herve Boutemy >Priority: Major > Fix For: 3.1.0 > > > consistent with Maven 3.3.1+ https://maven.apache.org/docs/history.html > Java 7 is EOL'ed since July 2021 https://javaalmanac.io/jdk/ : that's not > that far away, hellping a little bit people stuck here does not cost us so > much -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MWRAPPER-32) Use Maven core component in provided scope
[
https://issues.apache.org/jira/browse/MWRAPPER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWRAPPER-32:
--
Fix Version/s: 3.1.0
> Use Maven core component in provided scope
> --
>
> Key: MWRAPPER-32
> URL: https://issues.apache.org/jira/browse/MWRAPPER-32
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.1.0
>
>
> First dependency on {{maven-artifact-transfer}} should be removed because has
> many transitive dependency in compile scope to Maven core artifacts.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MWRAPPER-16) update mvnw scripts to launch target Maven mvn scripts, to enforce consistency
[ https://issues.apache.org/jira/browse/MWRAPPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MWRAPPER-16: -- Fix Version/s: 3.2.0 > update mvnw scripts to launch target Maven mvn scripts, to enforce consistency > -- > > Key: MWRAPPER-16 > URL: https://issues.apache.org/jira/browse/MWRAPPER-16 > Project: Maven Wrapper > Issue Type: Improvement > Components: Maven Wrapper Scripts >Affects Versions: 0.5.6, 3.1.0 >Reporter: Herve Boutemy >Priority: Major > Fix For: 3.2.0 > > > currently, wrapper scripts copied to user project mimic Maven scripts (search > .mvn, and so on), then launch wrapper.jar: at the end, wrapper.jar calls > installed Maven distribution Classworlds bootstrap to run Maven Java code > this may cause a discrepency between features supported by mvnw script vs > what would have been done by installed Maven mvn scripts > for example, when/if [https://github.com/apache/maven/pull/602] is done > To enforce consistency, mvnw should launch installed Maven mvn script at the > end, and let it do its full work as if it had been launched -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MWRAPPER-32) Use Maven core component in provided scope
[
https://issues.apache.org/jira/browse/MWRAPPER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456196#comment-17456196
]
Herve Boutemy commented on MWRAPPER-32:
---
isn't PR#5 a working first step?
> Use Maven core component in provided scope
> --
>
> Key: MWRAPPER-32
> URL: https://issues.apache.org/jira/browse/MWRAPPER-32
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.1.0
>
>
> First dependency on {{maven-artifact-transfer}} should be removed because has
> many transitive dependency in compile scope to Maven core artifacts.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (MWRAPPER-35) don't copy mvnwDebug* scripts by default
Herve Boutemy created MWRAPPER-35: - Summary: don't copy mvnwDebug* scripts by default Key: MWRAPPER-35 URL: https://issues.apache.org/jira/browse/MWRAPPER-35 Project: Maven Wrapper Issue Type: Task Components: Maven Wrapper Plugin Affects Versions: 3.1.0 Reporter: Herve Boutemy in MWRAPPER-28, we added mvnwDebug scripts, which are useful to be able to debug Maven when the build has an issue this seems like a exceptional case, that most projects won't really need: providing these scripts by default seems overkill then changing the default to not copy these scripts gives probably a better classical user experience -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MWRAPPER-35) don't copy mvnwDebug* scripts by default
[ https://issues.apache.org/jira/browse/MWRAPPER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MWRAPPER-35: -- Fix Version/s: 3.1.0 > don't copy mvnwDebug* scripts by default > > > Key: MWRAPPER-35 > URL: https://issues.apache.org/jira/browse/MWRAPPER-35 > Project: Maven Wrapper > Issue Type: Task > Components: Maven Wrapper Plugin >Affects Versions: 3.1.0 >Reporter: Herve Boutemy >Priority: Major > Fix For: 3.1.0 > > > in MWRAPPER-28, we added mvnwDebug scripts, which are useful to be able to > debug Maven when the build has an issue > this seems like a exceptional case, that most projects won't really need: > providing these scripts by default seems overkill > then changing the default to not copy these scripts gives probably a better > classical user experience -- This message was sent by Atlassian Jira (v8.20.1#820001)
