[jira] [Commented] (MNG-8084) Make the v4 api usable outside the Maven runtime
[ https://issues.apache.org/jira/browse/MNG-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832608#comment-17832608 ] Hudson commented on MNG-8084: - Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-8084-doc #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-8084-doc/2/ > Make the v4 api usable outside the Maven runtime > > > Key: MNG-8084 > URL: https://issues.apache.org/jira/browse/MNG-8084 > Project: Maven > Issue Type: New Feature >Reporter: Guillaume Nodet >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-962) Upgrade to Doxia Sitetools to 2.0.0-M10, Maven Reporting Impl/Exec 4.0.0-M8, Maven Fluido Skin 2.0.0-M6
[ https://issues.apache.org/jira/browse/MSITE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717978#comment-17717978 ] Hudson commented on MSITE-962: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-site-plugin » master #98 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/98/ > Upgrade to Doxia Sitetools to 2.0.0-M10, Maven Reporting Impl/Exec 4.0.0-M8, > Maven Fluido Skin 2.0.0-M6 > --- > > Key: MSITE-962 > URL: https://issues.apache.org/jira/browse/MSITE-962 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSCMPUB-53) Require Java 8
[ https://issues.apache.org/jira/browse/MSCMPUB-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696463#comment-17696463 ] Hudson commented on MSCMPUB-53: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-scm-publish-plugin » master #28 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-scm-publish-plugin/job/master/28/ > Require Java 8 > -- > > Key: MSCMPUB-53 > URL: https://issues.apache.org/jira/browse/MSCMPUB-53 > Project: Maven SCM Publish Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-927) Upgrade Parent to 39
[ https://issues.apache.org/jira/browse/MSITE-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687430#comment-17687430 ] Hudson commented on MSITE-927: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #60 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/60/ > Upgrade Parent to 39 > > > Key: MSITE-927 > URL: https://issues.apache.org/jira/browse/MSITE-927 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7670) Upgrade misc dependencies
[ https://issues.apache.org/jira/browse/MNG-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17678936#comment-17678936 ] Hudson commented on MNG-7670: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7670 #5 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7670/5/ > Upgrade misc dependencies > - > > Key: MNG-7670 > URL: https://issues.apache.org/jira/browse/MNG-7670 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.0-candidate > > > [INFO] The following dependencies in Dependency Management have newer > versions: > [INFO] com.google.guava:guava .. 30.1-jre -> > 31.1-jre > [INFO] org.apache.commons:commons-lang3 . 3.8.1 -> > 3.12.0 > [INFO] org.codehaus.plexus:plexus-classworlds 2.6.0 -> > 2.7.0 > [INFO] org.codehaus.plexus:plexus-component-annotations .. 2.1.0 -> > 2.1.1 > [INFO] org.codehaus.plexus:plexus-utils .. 3.4.2 -> > 3.5.0 > [INFO] org.hamcrest:hamcrest-core 1.3 -> > 2.2 > [INFO] org.hamcrest:hamcrest-library . 1.3 -> > 2.2 > [INFO] org.mockito:mockito-core 2.21.0 -> > 4.11.0 > [INFO] org.powermock:powermock-reflect ... 1.7.4 -> > 2.0.9 > [INFO] org.xmlunit:xmlunit-core .. 2.2.1 -> > 2.9.1 > [INFO] org.xmlunit:xmlunit-matchers .. 2.2.1 -> > 2.9.1 > Logback 1.3.x depends on SLF4J 2.x, Logback 1.4.x requires Java 11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-5857) Arguments from command line should override those in .mvn/maven.config
[ https://issues.apache.org/jira/browse/MNG-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652033#comment-17652033 ] Hudson commented on MNG-5857: - Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-5857_alt-1 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-5857_alt-1/2/ > Arguments from command line should override those in .mvn/maven.config > -- > > Key: MNG-5857 > URL: https://issues.apache.org/jira/browse/MNG-5857 > Project: Maven > Issue Type: Bug >Reporter: Dave Syer >Assignee: Michael Osipov >Priority: Major > Fix For: waiting-for-feedback > > > Because of the way the command line args are added at the *start* of the list > here: > [MavenCli#410|https://gitbox.apache.org/repos/asf?p=maven.git;a=blob;f=maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java;h=4d142ee4c9a7f4f1c6311fcc87aacb59ba14fc23;hb=HEAD#l410], > they get overwritten by the settings in .mvn/maven.config. I would have > thought this should be the other way round. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNGSITE-503) add .well-known/security.txt
[ https://issues.apache.org/jira/browse/MNGSITE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645856#comment-17645856 ] Hudson commented on MNGSITE-503: Build succeeded in Jenkins: Maven » Maven TLP » maven-site » master #194 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site/job/master/194/ > add .well-known/security.txt > > > Key: MNGSITE-503 > URL: https://issues.apache.org/jira/browse/MNGSITE-503 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Benjamin Marwell >Assignee: Benjamin Marwell >Priority: Major > Labels: security > > As per consensus on the mailing list (+1 from [~rmannibucau] and me), we > should add a file `.well-known/security.txt`. > I will prepare a PR. > References: > * [.well-known/security.txt at maven.apache.org > (mail-archive.com)|https://www.mail-archive.com/dev@maven.apache.org/msg128366.html] > * [.well-known/security.txt at maven.apache.org-Apache Mail > Archives|https://lists.apache.org/thread/tvfg1lx9nd72c9t4t4s3zlx6l0tpnmwy] > * [RFC 9116|https://datatracker.ietf.org/doc/html/rfc9116] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNGSITE-503) add .well-known/security.txt
[ https://issues.apache.org/jira/browse/MNGSITE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645850#comment-17645850 ] Hudson commented on MNGSITE-503: Build failed in Jenkins: Maven » Maven TLP » maven-site » PR-354 #10 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site/job/PR-354/10/ > add .well-known/security.txt > > > Key: MNGSITE-503 > URL: https://issues.apache.org/jira/browse/MNGSITE-503 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Benjamin Marwell >Assignee: Benjamin Marwell >Priority: Major > Labels: security > > As per consensus on the mailing list (+1 from [~rmannibucau] and me), we > should add a file `.well-known/security.txt`. > I will prepare a PR. > References: > * [.well-known/security.txt at maven.apache.org > (mail-archive.com)|https://www.mail-archive.com/dev@maven.apache.org/msg128366.html] > * [.well-known/security.txt at maven.apache.org-Apache Mail > Archives|https://lists.apache.org/thread/tvfg1lx9nd72c9t4t4s3zlx6l0tpnmwy] > * [RFC 9116|https://datatracker.ietf.org/doc/html/rfc9116] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-384) Allow to override streamLogsOnFailures parameter for m-invoker-p
[
https://issues.apache.org/jira/browse/MPOM-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645845#comment-17645845
]
Hudson commented on MPOM-384:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-parent » master #83
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-parent/job/master/83/
> Allow to override streamLogsOnFailures parameter for m-invoker-p
>
>
> Key: MPOM-384
> URL: https://issues.apache.org/jira/browse/MPOM-384
> Project: Maven POMs
> Issue Type: Improvement
> Components: maven
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: MAVEN-39
>
>
> When configuration is used, we can not override value by property.
> During local development I want to override {{streamLogsOnFailures}}
> parameter and simply read logs in IDE.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7505) Remove ReportingConverter
[
https://issues.apache.org/jira/browse/MNG-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645819#comment-17645819
]
Hudson commented on MNG-7505:
-
Build failed in Jenkins: Maven » Maven TLP » maven » master #155
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/155/
> Remove ReportingConverter
> -
>
> Key: MNG-7505
> URL: https://issues.apache.org/jira/browse/MNG-7505
> Project: Maven
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-alpha-3
>
>
> In m-site-p 3.7 configuration parameter {{reportPlugins}} was removed -
> MSITE-792
> So converting from reporting sections to {{reportPlugins}} option of m-site-p
> is not needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPOM-378) Using an SPDX identifier as the license name is recommended by Maven
[ https://issues.apache.org/jira/browse/MPOM-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645788#comment-17645788 ] Hudson commented on MPOM-378: - Build succeeded in Jenkins: Maven » Maven TLP » maven-apache-parent » master #78 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-apache-parent/job/master/78/ > Using an SPDX identifier as the license name is recommended by Maven > > > Key: MPOM-378 > URL: https://issues.apache.org/jira/browse/MPOM-378 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Reporter: Slawomir Jaranowski >Priority: Major > Fix For: ASF-29 > > > According to recommendation: https://maven.apache.org/pom.html#Licenses -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-383) Bump maven-dependency-plugin from 3.3.0 to 3.4.0
[ https://issues.apache.org/jira/browse/MPOM-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645785#comment-17645785 ] Hudson commented on MPOM-383: - Build succeeded in Jenkins: Maven » Maven TLP » maven-apache-parent » master #77 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-apache-parent/job/master/77/ > Bump maven-dependency-plugin from 3.3.0 to 3.4.0 > > > Key: MPOM-383 > URL: https://issues.apache.org/jira/browse/MPOM-383 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-29 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-382) Bump maven-install-plugin from 3.0.1 to 3.1.0
[ https://issues.apache.org/jira/browse/MPOM-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645784#comment-17645784 ] Hudson commented on MPOM-382: - Build succeeded in Jenkins: Maven » Maven TLP » maven-apache-parent » master #76 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-apache-parent/job/master/76/ > Bump maven-install-plugin from 3.0.1 to 3.1.0 > - > > Key: MPOM-382 > URL: https://issues.apache.org/jira/browse/MPOM-382 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-29 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-381) Bump maven-release-plugin from 3.0.0-M6 to 3.0.0-M7
[ https://issues.apache.org/jira/browse/MPOM-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645756#comment-17645756 ] Hudson commented on MPOM-381: - Build succeeded in Jenkins: Maven » Maven TLP » maven-apache-parent » master #75 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-apache-parent/job/master/75/ > Bump maven-release-plugin from 3.0.0-M6 to 3.0.0-M7 > --- > > Key: MPOM-381 > URL: https://issues.apache.org/jira/browse/MPOM-381 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-29 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-380) Bump maven-ear-plugin from 3.2.0 to 3.3.0
[ https://issues.apache.org/jira/browse/MPOM-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645755#comment-17645755 ] Hudson commented on MPOM-380: - Build succeeded in Jenkins: Maven » Maven TLP » maven-apache-parent » master #74 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-apache-parent/job/master/74/ > Bump maven-ear-plugin from 3.2.0 to 3.3.0 > - > > Key: MPOM-380 > URL: https://issues.apache.org/jira/browse/MPOM-380 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-29 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSKINS-198) Don't apply font size for in heading elements
[
https://issues.apache.org/jira/browse/MSKINS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645695#comment-17645695
]
Hudson commented on MSKINS-198:
---
Build succeeded in Jenkins: Maven » Maven TLP » maven-fluido-skin » master #42
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-fluido-skin/job/master/42/
> Don't apply font size for in heading elements
> --
>
> Key: MSKINS-198
> URL: https://issues.apache.org/jira/browse/MSKINS-198
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-1.11.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: fluido-next-release
>
> Attachments: image-2022-12-10-23-59-21-326.png,
> image-2022-12-11-00-01-12-584.png
>
>
> When using Markdown and heading contains code elements with backtick those
> are converted to {{}} inside {{}} elements. Bootstrap is not
> aware that this is possible and overrides the font size of the heading
> element to the one of {{{}{}}}. An ugly example is the Maven Resolver
> page:
> !image-2022-12-10-23-59-21-326.png!
> The {{-X}} is not expected to look that tiny. Unset the font size of {{ />}} here.
> Expected:
> !image-2022-12-11-00-01-12-584.png!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSKINS-197) CSS never applied to and in section elements
[ https://issues.apache.org/jira/browse/MSKINS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645691#comment-17645691 ] Hudson commented on MSKINS-197: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-fluido-skin » master #40 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-fluido-skin/job/master/40/ > CSS never applied to and in section elements > - > > Key: MSKINS-197 > URL: https://issues.apache.org/jira/browse/MSKINS-197 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.11.1 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: fluido-next-release > > > [This > line|https://github.com/apache/maven-fluido-skin/blob/7fffaa7e466f1b9f54af2bbe3280d67d3e279451/src/main/resources/css/maven-base.css#L22] > applies CSS rules to non-existing classes throughout the skin, I assume that > those were meant for section blocks, not classes. Moreover, the rules are > duplicated for some reason. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCOMPILER-501) compileSourceRoots parameter should be writable
[
https://issues.apache.org/jira/browse/MCOMPILER-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645450#comment-17645450
]
Hudson commented on MCOMPILER-501:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-compiler-plugin » master
#97
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-compiler-plugin/job/master/97/
> compileSourceRoots parameter should be writable
>
>
> Key: MCOMPILER-501
> URL: https://issues.apache.org/jira/browse/MCOMPILER-501
> Project: Maven Compiler Plugin
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.11.0
>
>
> {{compileSourceRoots}} is used many times in configuration, eg to build
> project for multi release in single project pattern:
> [https://github.com/apache/maven-compiler-plugin/blob/master/src/it/multirelease-patterns/singleproject-runtime/pom.xml]
> so should be writable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7578) Building Linux image on Windows impossible (patch incuded)
[
https://issues.apache.org/jira/browse/MNG-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645199#comment-17645199
]
Hudson commented on MNG-7578:
-
Build failed in Jenkins: Maven » Maven TLP » maven » master #151
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/151/
> Building Linux image on Windows impossible (patch incuded)
> --
>
> Key: MNG-7578
> URL: https://issues.apache.org/jira/browse/MNG-7578
> Project: Maven
> Issue Type: Bug
> Components: Core, Toolchains
>Affects Versions: 3.8.6
>Reporter: Eugen Labun
>Assignee: Maarten Mulders
>Priority: Major
>
> If you try to find `javac` in a Linux JDK using `Toolchain.findTool()`
> method, this will fail when the build is running on Windows, since the
> implementation
> [JavaToolchainImpl#findTool()|https://github.com/apache/maven/blob/maven-3.8.6/maven-core/src/main/java/org/apache/maven/toolchain/java/JavaToolchainImpl.java#L74-L86]
> appends ".exe" to the toolName (causing `javac.exe` is not found):
> {code:java}
> private static File findTool( String toolName, File installFolder )
> {
> File bin = new File( installFolder, "bin" ); //NOI18N
> if ( bin.exists() )
> {
> File tool = new File( bin, toolName + ( Os.isFamily( "windows" )
> ? ".exe" : "" ) ); // NOI18N
> if ( tool.exists() )
> {
> return tool;
> }
> }
> return null;
>}
> {code}
> The current workaround is to manually add a fake `javac.exe` file to the JDK
> `bin` directory. See [tool chain issue (building linux image on windows
> machine)|https://github.com/moditect/moditect/issues/107] in moditect project.
> The `findTool` method could yet easily be changed to search for exact
> `toolName` as requested, with a fallback to `toolName.exe` for backward
> compatibility:
> {code:java}
> private static File findTool( String toolName, File installFolder )
> {
> File bin = new File( installFolder, "bin" );
> if ( bin.exists() )
> {
> File tool = new File( bin, toolName );
> if ( tool.exists() )
> {
> return tool;
> }
> File toolExe = new File( bin, toolName + ".exe" );
> if ( toolExe.exists() )
> {
> return toolExe;
> }
> }
> return null;
>}
> {code}
> This would solve the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPOM-377) Add space before close empty elements in poms
[ https://issues.apache.org/jira/browse/MPOM-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645190#comment-17645190 ] Hudson commented on MPOM-377: - Build failed in Jenkins: Maven » Maven TLP » maven-parent » master #72 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-parent/job/master/72/ > Add space before close empty elements in poms > - > > Key: MPOM-377 > URL: https://issues.apache.org/jira/browse/MPOM-377 > Project: Maven POMs > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-38 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: MAVEN-39 > > > Release plugin add space before close empty elements, > it is a bug in release plugin - content of pom should be reformatted. > As workaround we can add a space by spotless also. > Without it release can break. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCOMPILER-512) Defining maven.compiler.release as empty string ends with NumberFormatException in testCompileMojo
[
https://issues.apache.org/jira/browse/MCOMPILER-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644681#comment-17644681
]
Hudson commented on MCOMPILER-512:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-compiler-plugin » master
#96
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-compiler-plugin/job/master/96/
> Defining maven.compiler.release as empty string ends with
> NumberFormatException in testCompileMojo
> --
>
> Key: MCOMPILER-512
> URL: https://issues.apache.org/jira/browse/MCOMPILER-512
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.6.0, 3.10.1
>Reporter: Holger Mense
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.11.0
>
> Attachments: showcase.zip
>
>
> When {{maven.compiler.release}} is set to an empty string, a
> {{NumberFormatException}} is thrown when trying to compile tests.
> See attached [^showcase.zip] for a minimal example. Calling {{mvn test}} in
> subdirectory {{HelloWorld/}} produces the following:
> {noformat}
> [HelloWorld/] $ mvn clean test -e
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< example:helloworld
> >-
> [INFO] Building helloworld 1.0.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ helloworld ---
> [INFO] Deleting C:\DATA\temp\maven-compiler-issue\HelloWorld\target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> helloworld ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory
> C:\DATA\temp\maven-compiler-issue\HelloWorld\src\main\resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @
> helloworld ---
> [INFO] Changes detected - recompiling the module!
> [WARNING] File encoding has not been set, using platform encoding Cp1252,
> i.e. build is platform dependent!
> [INFO] Compiling 1 source file to
> C:\DATA\temp\maven-compiler-issue\HelloWorld\target\classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
> helloworld ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory
> C:\DATA\temp\maven-compiler-issue\HelloWorld\src\test\resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.10.1:testCompile (default-testCompile) @
> helloworld ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.690 s
> [INFO] Finished at: 2022-11-30T16:05:57+01:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile
> (default-testCompile) on project helloworld: Execution default-testCompile of
> goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile
> failed: For input string: "" -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile
> (default-testCompile) on project helloworld: Execution default-testCompile of
> goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile
> failed: For input string: ""
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:375)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:351)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:171)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:163)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
> at org.apache.maven.DefaultMaven.doExecute
[jira] [Commented] (MSHARED-1171) New IntelliJ code style formatter
[ https://issues.apache.org/jira/browse/MSHARED-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643965#comment-17643965 ] Hudson commented on MSHARED-1171: - Build succeeded in Jenkins: Maven » Maven TLP » maven-shared-resources » master #18 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-shared-resources/job/master/18/ > New IntelliJ code style formatter > - > > Key: MSHARED-1171 > URL: https://issues.apache.org/jira/browse/MSHARED-1171 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-resources >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-shared-resources-6 > > > Parent pom 38 introduce new code style, so add also new formatter for IDE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-376) Spotless importOrder should be taken into consideration
[ https://issues.apache.org/jira/browse/MPOM-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643556#comment-17643556 ] Hudson commented on MPOM-376: - Build succeeded in Jenkins: Maven » Maven TLP » maven-parent » master #71 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-parent/job/master/71/ > Spotless importOrder should be taken into consideration > --- > > Key: MPOM-376 > URL: https://issues.apache.org/jira/browse/MPOM-376 > Project: Maven POMs > Issue Type: Bug > Components: maven >Affects Versions: MAVEN-38 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: MAVEN-39 > > > Configuration items in spotless should be in correct order. > Currently importOrder is not taken into consideration > So imports are sorted in wrong way, not corresponding to configuration. > https://github.com/diffplug/spotless/issues/1417 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7576) Restore compatibility with maven 3
[
https://issues.apache.org/jira/browse/MNG-7576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643458#comment-17643458
]
Hudson commented on MNG-7576:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #150
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/150/
> Restore compatibility with maven 3
> --
>
> Key: MNG-7576
> URL: https://issues.apache.org/jira/browse/MNG-7576
> Project: Maven
> Issue Type: Task
>Affects Versions: 4.0.0-alpha-2
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-alpha-3
>
>
> {{MavenBuildTimestamp}}
> https://github.com/apache/maven/commit/18eff3baeb899ddd27b34635c8f0d7e47f5c027b
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7618) Use goalPrefix instead of artifactId to display mojos being executed
[
https://issues.apache.org/jira/browse/MNG-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643444#comment-17643444
]
Hudson commented on MNG-7618:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #149
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/149/
> Use goalPrefix instead of artifactId to display mojos being executed
> -
>
> Key: MNG-7618
> URL: https://issues.apache.org/jira/browse/MNG-7618
> Project: Maven
> Issue Type: Task
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-alpha-3
>
>
> The main problem is that the information displayed when starting a mojo looks
> like:
> {code:java}
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> camel ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @ camel
> ---
> [INFO]
> {code}
> However, if you try to execute {{{}maven-enforcer-plugin:3.0.0:enforce{}}},
> you end up with the following:
> {code:java}
> [INFO] BuildTimeEventSpy is registered.
> [INFO] Scanning for projects...
> Downloading from apache.snapshots:
> https://repository.apache.org/snapshots/maven-enforcer-plugin/3.0.0/maven-metadata.xml
> Downloading from central:
> https://repo.maven.apache.org/maven2/maven-enforcer-plugin/3.0.0/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.879 s
> [INFO] Finished at: 2022-12-03T12:12:40+01:00
> [INFO]
>
> [ERROR] Error resolving version for plugin 'maven-enforcer-plugin:3.0.0' from
> the repositories [local (/Users/gnodet/.m2/repository), apache.snapshots
> (https://repository.apache.org/snapshots/), central
> (https://repo.maven.apache.org/maven2)]: Plugin not found in any plugin
> repository -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException
> {code}
>
> I suggest to change the display to the {{pluginPrefix}} which gives
> {code}
> [INFO] ---< org.apache.camel:camel
> >---
> [INFO] Building Camel 4.0.0-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ pom
> ]-
> [WARN] Parameter 'reportPlugins' is unknown for plugin
> 'maven-site-plugin:3.11.0:attach-descriptor (attach-descriptor)'
> [INFO]
> [INFO] --- enforcer:3.0.0:enforce (enforce-maven-version) @ camel ---
> [INFO]
> [INFO] --- enforcer:3.0.0:enforce (enforce-java-version) @ camel ---
> [INFO]
> [INFO] --- enforcer:3.0.0:enforce (enforce-maven) @ camel ---
> [INFO]
> {code}
> which can then be easily executed:
> {code}
> ➜ maven git:(build-improvements) ✗ mvn -N -f ../camel flatten:1.2.5:flatten
> [INFO] BuildTimeEventSpy is registered.
> [INFO] Processing build on daemon 56c20cb8
> [INFO] Scanning for projects...
> [INFO] BuildTimeEventSpy is registered.
> [INFO]
> [INFO] Using the SmartBuilder implementation with a thread count of 9
> [INFO] Task segments : [flatten:1.2.5:flatten]
> [INFO] Build maximum degree of concurrency is 9
> [INFO] Total number of projects is 1
> [INFO]
> [INFO] ---< org.apache.camel:camel
> >---
> [INFO] Building Camel 4.0.0-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- flatten:1.2.5:flatten (default-cli) @ camel ---
> [INFO] Generating flattened POM of project
> org.apache.camel:camel:pom:4.0.0-SNAPSHOT...
> [INFO] Segment walltime 0 s, segment projects service time 0 s,
> effective/maximum degree of concurrency 0.97/9
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.025 s (Wall Clock)
> [INFO] Finished at: 2022-12-03T12:14:29+01:00
> [INFO]
>
> ➜ maven git:(build-improvements) ✗
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7619) Maven should explain why an artifact is present in local repository
[
https://issues.apache.org/jira/browse/MNG-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643427#comment-17643427
]
Hudson commented on MNG-7619:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #148
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/148/
> Maven should explain why an artifact is present in local repository
> ---
>
> Key: MNG-7619
> URL: https://issues.apache.org/jira/browse/MNG-7619
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.0, 4.0.x-candidate, 4.0.0-alpha-3
>
>
> Ability to make Maven record:
> * why given artifact is present in local repository
> * record reverse dep tree how this artifact got resolved
> This is mostly for detecting dependency resolution anomalies, ideally best
> combined with {{-Dmaven.repo.local}} when you use new/empty local repo to
> build a project. After the build, you will end up with reverse dep trees in
> {{.tracking}} directories for each artifact.
> To enable, pass {{-Dmaven.repo.local.recordReverseTree}} on CLI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7619) Maven should explain why an artifact is present in local repository
[
https://issues.apache.org/jira/browse/MNG-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643423#comment-17643423
]
Hudson commented on MNG-7619:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #96
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/96/
> Maven should explain why an artifact is present in local repository
> ---
>
> Key: MNG-7619
> URL: https://issues.apache.org/jira/browse/MNG-7619
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.0, 4.0.x-candidate, 4.0.0-alpha-3
>
>
> Ability to make Maven record:
> * why given artifact is present in local repository
> * record reverse dep tree how this artifact got resolved
> This is mostly for detecting dependency resolution anomalies, ideally best
> combined with {{-Dmaven.repo.local}} when you use new/empty local repo to
> build a project. After the build, you will end up with reverse dep trees in
> {{.tracking}} directories for each artifact.
> To enable, pass {{-Dmaven.repo.local.recordReverseTree}} on CLI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPOM-373) Execute spotless before rat
[
https://issues.apache.org/jira/browse/MPOM-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643316#comment-17643316
]
Hudson commented on MPOM-373:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-parent » master #69
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-parent/job/master/69/
> Execute spotless before rat
> ---
>
> Key: MPOM-373
> URL: https://issues.apache.org/jira/browse/MPOM-373
> Project: Maven POMs
> Issue Type: Improvement
> Components: maven
>Affects Versions: MAVEN-38
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: MAVEN-39
>
>
> {{apache-rat-plugin:check}} should be executed after a reformatting with
> {{spotless-maven-plugin:apply}}. Currently the latter is executed in phase
> {{process-sourcess}} while the former is executed in {{validate}}
> (https://github.com/apache/creadur-rat/blob/acc6141d3bfbea4c1811604fa5668b1572e85898/apache-rat-plugin/src/main/java/org/apache/rat/mp/RatCheckMojo.java#L48).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-444) JavadocLinkGenerator.createLink: Support nested binary class names
[
https://issues.apache.org/jira/browse/MPLUGIN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643264#comment-17643264
]
Hudson commented on MPLUGIN-444:
Build succeeded in Jenkins: Maven » Maven TLP » maven-plugin-tools » master #93
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-tools/job/master/93/
> JavadocLinkGenerator.createLink: Support nested binary class names
> --
>
> Key: MPLUGIN-444
> URL: https://issues.apache.org/jira/browse/MPLUGIN-444
> Project: Maven Plugin Tools
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: next-release
>
>
> Currently all binary names containing a dollar "$" throw an
> {{IllegalArgumentException}} when being invoked with
> {{JavadocLinkGenerator.createLink(...)}}. Actually member classes should be
> supported as links to their Javadoc can be reliably constructed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7611) java.lang.IllegalStateException: Required Java version 1.8 is not met by current version: 17.0.5
[
https://issues.apache.org/jira/browse/MNG-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643242#comment-17643242
]
Hudson commented on MNG-7611:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-plugin-tools » master #91
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-tools/job/master/91/
> java.lang.IllegalStateException: Required Java version 1.8 is not met by
> current version: 17.0.5
>
>
> Key: MNG-7611
> URL: https://issues.apache.org/jira/browse/MNG-7611
> Project: Maven
> Issue Type: Task
>Reporter: Guillaume Nodet
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-3
>
>
> {code:java}
> Caused by: java.lang.IllegalStateException: Required Java version 1.8 is not
> met by current version: 17.0.5
>at
> org.apache.maven.plugin.internal.MavenPluginJavaPrerequisiteChecker.accept(MavenPluginJavaPrerequisiteChecker.java:38)
>at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.lambda$checkPrerequisites$1(DefaultMavenPluginManager.java:289)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-443) Javadoc reference containing a link label with spaces are not detected
[
https://issues.apache.org/jira/browse/MPLUGIN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643243#comment-17643243
]
Hudson commented on MPLUGIN-443:
Build succeeded in Jenkins: Maven » Maven TLP » maven-plugin-tools » master #91
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-tools/job/master/91/
> Javadoc reference containing a link label with spaces are not detected
> --
>
> Key: MPLUGIN-443
> URL: https://issues.apache.org/jira/browse/MPLUGIN-443
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: API
>Affects Versions: 3.7.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: next-release
>
>
> For example the following link tag is not properly parsed:
> {code}
> {@link #member label with spaces}
> {code}
> and leads to the following exception
> {code}
> java.lang.IllegalArgumentException: Invalid format of javadoc reference:
> #member label with spaces
> at
> org.apache.maven.tools.plugin.javadoc.JavadocReference.parse(JavadocReference.java:74)
> ...
> {code}
> According to
> https://docs.oracle.com/en/java/javase/17/docs/specs/javadoc/doc-comment-spec.html#link
> this should be valid though as the link tag ends only with the '}'
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNGSITE-501) Clarify JDK activation element
[
https://issues.apache.org/jira/browse/MNGSITE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643195#comment-17643195
]
Hudson commented on MNGSITE-501:
Build succeeded in Jenkins: Maven » Maven TLP » maven-site » master #186
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site/job/master/186/
> Clarify JDK activation element
> --
>
> Key: MNGSITE-501
> URL: https://issues.apache.org/jira/browse/MNGSITE-501
> Project: Maven Project Web Site
> Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Both in [https://maven.apache.org/pom.html#Activation] and
> [https://maven.apache.org/guides/introduction/introduction-to-profiles.html#details-on-profile-activation]
> the {{jdk}} element needs clarification that not all values are interpreted
> as ranges (in contrast to what the referenced version range specification
> from enforcer maven plugin in
> [https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html] says).
> Actually there are three different kind of values supported:
> # Version ranges (if the value starts with either "[" or "(")
> # A negated prefix (if the value starts with "!")
> # A (non-negated) prefix for all other cases
> This can be seen in
> [https://github.com/apache/maven/blob/001eef8452b38110a2557446aa81b8fb1ff35f92/maven-model-builder/src/main/java/org/apache/maven/model/profile/activation/JdkVersionProfileActivator.java#L69]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7609) Clarify documentation of extension descriptor
[
https://issues.apache.org/jira/browse/MNG-7609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643187#comment-17643187
]
Hudson commented on MNG-7609:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #147
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/147/
> Clarify documentation of extension descriptor
> -
>
> Key: MNG-7609
> URL: https://issues.apache.org/jira/browse/MNG-7609
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-3
>
>
> The extension descriptor is documented in
> https://maven.apache.org/ref/3-LATEST/maven-core/extension.html based on the
> MDO file at
> https://github.com/apache/maven/blob/master/maven-core/src/main/mdo/extension.mdo.
> It is lacking important information such as
> - how are subpackages and wildcards handled in {{exportedPackages}}?
> - how can one export individual classes via {{exportedPackages}} (compare
> with
> https://github.com/apache/maven/blob/c6ecff9923088d854d4621e17d602f1c70dda806/maven-core/src/main/mdo/extension.mdo#L50)
> - how are {{exportedPackages}} and {{exportedArtifacts}} related? Are they
> just merged or are they combined in some other way?
> The better extension descriptor documentation should finally be linked also
> from
> https://github.com/apache/maven/blob/master/maven-core/src/site/apt/core-extensions.apt.vm,
> as well as from
> https://maven.apache.org/guides/mini/guide-maven-classloading.html#API_Classloader
> and https://maven.apache.org/guides/mini/guide-using-extensions.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643013#comment-17643013 ] Hudson commented on MENFORCER-438: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-enforcer » master #82 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/82/ > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MENFORCER-411) DependencyConvergence should support including/excluding certain dependencies
[ https://issues.apache.org/jira/browse/MENFORCER-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643009#comment-17643009 ] Hudson commented on MENFORCER-411: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-enforcer » master #81 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/81/ > DependencyConvergence should support including/excluding certain dependencies > - > > Key: MENFORCER-411 > URL: https://issues.apache.org/jira/browse/MENFORCER-411 > Project: Maven Enforcer Plugin > Issue Type: New Feature > Components: Standard Rules >Affects Versions: 3.1.0 >Reporter: Forrest Feaser >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > Original Estimate: 4h > Remaining Estimate: 4h > > It would be nice if the DependencyConvergence rule could specify certain > dependencies that should/should not fail the build. This might be useful if > your project has a lot of dependency conflicts, but you know there are just a > few troublesome ones that cause issues, and you don't want to resolve the > conflicts for your entire project. > Here is my PR: https://github.com/apache/maven-enforcer/pull/136 > Do I need to sign the Contributor License Agreement for this? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MWRAPPER-84) Update documentation about shells
[
https://issues.apache.org/jira/browse/MWRAPPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642932#comment-17642932
]
Hudson commented on MWRAPPER-84:
Build unstable in Jenkins: Maven » Maven TLP » maven-wrapper » master #54
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-wrapper/job/master/54/
> Update documentation about shells
> -
>
> Key: MWRAPPER-84
> URL: https://issues.apache.org/jira/browse/MWRAPPER-84
> Project: Maven Wrapper
> Issue Type: Task
>Affects Versions: 3.1.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.2.0
>
>
> https://maven.apache.org/wrapper/ says:
> {noformat}
> For all those *nix operating systems, various shells should work including
> sh
> bash
> dash
> zsh
> {noformat}
> This section must be removed an replaced that the wrapper script required a
> POSIX-compatible Bourne shell.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-831) Remove not used dependencies / Replace parts
[
https://issues.apache.org/jira/browse/MDEP-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642908#comment-17642908
]
Hudson commented on MDEP-831:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin »
master #71
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/master/71/
> Remove not used dependencies / Replace parts
>
>
> Key: MDEP-831
> URL: https://issues.apache.org/jira/browse/MDEP-831
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.3.0
>Reporter: Karl Heinz Marbaise
>Assignee: Elliotte Rusty Harold
>Priority: Minor
> Fix For: version-next
>
>
> Currently the dependency is not used at all:
> {code:xml}
>
> commons-beanutils
> commons-beanutils
> 1.9.4
>
> {code}
> The dependency is only used for a single method:
> {code:xml}
>
> org.apache.commons
> commons-collections4
> 4.2
>
> {code}
> The dependency is only used for two methods of StringUtils.
> {code:xml}
>
> org.apache.commons
> commons-lang3
> 3.12.0
>
> {code}
> The dependency is only used in tests for deleting a directory.
> {code:xml}
>
> commons-io
> commons-io
> 2.11.0
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7612) Chained Local Repository
[ https://issues.apache.org/jira/browse/MNG-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642866#comment-17642866 ] Hudson commented on MNG-7612: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #145 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/145/ > Chained Local Repository > - > > Key: MNG-7612 > URL: https://issues.apache.org/jira/browse/MNG-7612 > Project: Maven > Issue Type: New Feature > Components: Artifacts and Repositories >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > New feature: Chained Local Repository Manager (CLRM). > This new feature is not something one would use in production, is more > targeted to Integration Test isolation. > User story: ITs usually are run as part of Maven build – lets call it "outer > build" – that may build among other things, plugins and some artifacts needed > for the ITs. The ITs itself – let's call them "inner build" – should run in > isolated environment. > Problem: the "outer build" is usually affected by user environment > (settings.xml, use of MRM, and may use user own local repository unless > alternate specified) but also we do not want user MRM to be altered by IT > runs. The "inner build" on the other hand, may fail if use same LRM as "outer > build", as they are isolated, so they do not use settings.xml from the outer > build, may not use MRM and same remote repository IDs, and all these may lead > to mysterious "artifact not found" problems. Typically, outer build may use > MRM that defines mirrorOf with ID "my-mrm", while inner would use defaults, > where only remote repository is "central": this leads that user LRM gets > populated with artifacts available from "my-mrm" remote repository, while > inner build would know only about "central" remote repository. Enhanced LRM > (default since Maven 3.0) would refuse to serve up these artifacts. > Solution is CLRM: with CLRM user is able to specify isolated LRM for ITs, > while still making artifacts from outer LRM "visible" (discoverable) for the > IT build. Inner build uses isolated LRM solely, but for resolution purposes > still is able to resolve from outer LRM, where outer build might deployed > artifacts, plugins used by IT inner build. > Technical remark: CLRM defines "head" LRM, and list of LRM as "tail". Almost > all methods are delegated toward "head", except for find methods (metadata > and artifact), exposing tail LRM contents for artifact resolution. Also, CLRM > is *able* to enforce artifact availability (as explained above), but in most > cases (at least in IT user story), one would want to inhibit this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7612) Chained Local Repository
[ https://issues.apache.org/jira/browse/MNG-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642803#comment-17642803 ] Hudson commented on MNG-7612: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-897 #3 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-897/3/ > Chained Local Repository > - > > Key: MNG-7612 > URL: https://issues.apache.org/jira/browse/MNG-7612 > Project: Maven > Issue Type: New Feature > Components: Artifacts and Repositories >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > New feature: Chained Local Repository Manager (CLRM). > This new feature is not something one would use in production, is more > targeted to Integration Test isolation. > User story: ITs usually are run as part of Maven build – lets call it "outer > build" – that may build among other things, plugins and some artifacts needed > for the ITs. The ITs itself – let's call them "inner build" – should run in > isolated environment. > Problem: the "outer build" is usually affected by user environment > (settings.xml, use of MRM, and may use user own local repository unless > alternate specified) but also we do not want user MRM to be altered by IT > runs. The "inner build" on the other hand, may fail if use same LRM as "outer > build", as they are isolated, so they do not use settings.xml from the outer > build, may not use MRM and same remote repository IDs, and all these may lead > to mysterious "artifact not found" problems. Typically, outer build may use > MRM that defines mirrorOf with ID "my-mrm", while inner would use defaults, > where only remote repository is "central": this leads that user LRM gets > populated with artifacts available from "my-mrm" remote repository, while > inner build would know only about "central" remote repository. Enhanced LRM > (default since Maven 3.0) would refuse to serve up these artifacts. > Solution is CLRM: with CLRM user is able to specify isolated LRM for ITs, > while still making artifacts from outer LRM "visible" (discoverable) for the > IT build. Inner build uses isolated LRM solely, but for resolution purposes > still is able to resolve from outer LRM, where outer build might deployed > artifacts, plugins used by IT inner build. > Technical remark: CLRM defines "head" LRM, and list of LRM as "tail". Almost > all methods are delegated toward "head", except for find methods (metadata > and artifact), exposing tail LRM contents for artifact resolution. Also, CLRM > is *able* to enforce artifact availability (as explained above), but in most > cases (at least in IT user story), one would want to inhibit this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNGSITE-499) Publish build-cache-extension schemas
[ https://issues.apache.org/jira/browse/MNGSITE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642797#comment-17642797 ] Hudson commented on MNGSITE-499: Build succeeded in Jenkins: Maven » Maven TLP » maven-site » master #184 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site/job/master/184/ > Publish build-cache-extension schemas > - > > Key: MNGSITE-499 > URL: https://issues.apache.org/jira/browse/MNGSITE-499 > Project: Maven Project Web Site > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCOMPILER-457) Change showWarnings to true by default
[
https://issues.apache.org/jira/browse/MCOMPILER-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642694#comment-17642694
]
Hudson commented on MCOMPILER-457:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-compiler-plugin » master
#95
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-compiler-plugin/job/master/95/
> Change showWarnings to true by default
> --
>
> Key: MCOMPILER-457
> URL: https://issues.apache.org/jira/browse/MCOMPILER-457
> Project: Maven Compiler Plugin
> Issue Type: Improvement
>Reporter: Thomas Broyer
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.11.0
>
>
> I see no reason to hide warnings by default, and setting {{failOnWarning}} to
> {{true}} will be useless without also setting {{showWarnings}} to {{true}};
> but you'll actually never know until you *actually* expect a warning (and
> build failure) and doesn't see it. Setting {{failOnWarning}} preventively
> without also setting {{showWarnings}} thus won't prevent anything; even if
> you also pass a strict {{-Xlint:all}} (because {{-nowarn}} has precedence
> apparently).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-917) Upgrade components and plugin in ITs
[ https://issues.apache.org/jira/browse/MSITE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642692#comment-17642692 ] Hudson commented on MSITE-917: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #50 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/50/ > Upgrade components and plugin in ITs > > > Key: MSITE-917 > URL: https://issues.apache.org/jira/browse/MSITE-917 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M4 > > > * Upgrade Jetty to 9.4.49.v20220914 > * Maven PMD Plugin to 3.19.0 > * Maven JXR Plugin to 3.3.0 > * Maven PIR Plugin to 3.4.1 > * Maven Surefire Plugin to 3.0.0-M7 > * Maven Reporting Impl to 4.0.0-M3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-919) Upgrade Maven Reporting Exec to 2.0.0-M3
[ https://issues.apache.org/jira/browse/MSITE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642691#comment-17642691 ] Hudson commented on MSITE-919: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #50 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/50/ > Upgrade Maven Reporting Exec to 2.0.0-M3 > > > Key: MSITE-919 > URL: https://issues.apache.org/jira/browse/MSITE-919 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCOMPILER-457) Change showWarnings to true by default
[
https://issues.apache.org/jira/browse/MCOMPILER-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642690#comment-17642690
]
Hudson commented on MCOMPILER-457:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-compiler-plugin » master
#94
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-compiler-plugin/job/master/94/
> Change showWarnings to true by default
> --
>
> Key: MCOMPILER-457
> URL: https://issues.apache.org/jira/browse/MCOMPILER-457
> Project: Maven Compiler Plugin
> Issue Type: Improvement
>Reporter: Thomas Broyer
>Assignee: Slawomir Jaranowski
>Priority: Major
>
> I see no reason to hide warnings by default, and setting {{failOnWarning}} to
> {{true}} will be useless without also setting {{showWarnings}} to {{true}};
> but you'll actually never know until you *actually* expect a warning (and
> build failure) and doesn't see it. Setting {{failOnWarning}} preventively
> without also setting {{showWarnings}} thus won't prevent anything; even if
> you also pass a strict {{-Xlint:all}} (because {{-nowarn}} has precedence
> apparently).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7609) Clarify documentation of extension descriptor
[
https://issues.apache.org/jira/browse/MNG-7609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642634#comment-17642634
]
Hudson commented on MNG-7609:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » PR-896 #2
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-896/2/
> Clarify documentation of extension descriptor
> -
>
> Key: MNG-7609
> URL: https://issues.apache.org/jira/browse/MNG-7609
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Reporter: Konrad Windszus
>Priority: Major
>
> The extension descriptor is documented in
> https://maven.apache.org/ref/3-LATEST/maven-core/extension.html based on the
> MDO file at
> https://github.com/apache/maven/blob/master/maven-core/src/main/mdo/extension.mdo.
> It is lacking important information such as
> - how are subpackages and wildcards handled in {{exportedPackages}}?
> - how can one export individual classes via {{exportedPackages}} (compare
> with
> https://github.com/apache/maven/blob/c6ecff9923088d854d4621e17d602f1c70dda806/maven-core/src/main/mdo/extension.mdo#L50)
> - how are {{exportedPackages}} and {{exportedArtifacts}} related? Are they
> just merged or are they combined in some other way?
> The better extension descriptor documentation should finally be linked also
> from
> https://github.com/apache/maven/blob/master/maven-core/src/site/apt/core-extensions.apt.vm,
> as well as from
> https://maven.apache.org/guides/mini/guide-maven-classloading.html#API_Classloader
> and https://maven.apache.org/guides/mini/guide-using-extensions.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7608) Make Resolver native transport the default in Maven4
[ https://issues.apache.org/jira/browse/MNG-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642635#comment-17642635 ] Hudson commented on MNG-7608: - Build unstable in Jenkins: Maven » Maven TLP » maven » PR-896 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-896/2/ > Make Resolver native transport the default in Maven4 > > > Key: MNG-7608 > URL: https://issues.apache.org/jira/browse/MNG-7608 > Project: Maven > Issue Type: Improvement >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.x-candidate, 4.0.0 > > > The ancient Wagon should be phased out, and "native" resolver transport > should be the default in Maven4. This in start halves the HTTP request count > toward Maven Central and any major MRM. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7612) Chained Local Repository
[ https://issues.apache.org/jira/browse/MNG-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642624#comment-17642624 ] Hudson commented on MNG-7612: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #95 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/95/ > Chained Local Repository > - > > Key: MNG-7612 > URL: https://issues.apache.org/jira/browse/MNG-7612 > Project: Maven > Issue Type: New Feature > Components: Artifacts and Repositories >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > New feature: Chained Local Repository Manager (CLRM). > This new feature is not something one would use in production, is more > targeted to Integration Test isolation. > User story: ITs usually are run as part of Maven build – lets call it "outer > build" – that may build among other things, plugins and some artifacts needed > for the ITs. The ITs itself – let's call them "inner build" – should run in > isolated environment. > Problem: the "outer build" is usually affected by user environment > (settings.xml, use of MRM, and may use user own local repository unless > alternate specified) but also we do not want user MRM to be altered by IT > runs. The "inner build" on the other hand, may fail if use same LRM as "outer > build", as they are isolated, so they do not use settings.xml from the outer > build, may not use MRM and same remote repository IDs, and all these may lead > to mysterious "artifact not found" problems. Typically, outer build may use > MRM that defines mirrorOf with ID "my-mrm", while inner would use defaults, > where only remote repository is "central": this leads that user LRM gets > populated with artifacts available from "my-mrm" remote repository, while > inner build would know only about "central" remote repository. Enhanced LRM > (default since Maven 3.0) would refuse to serve up these artifacts. > Solution is CLRM: with CLRM user is able to specify isolated LRM for ITs, > while still making artifacts from outer LRM "visible" (discoverable) for the > IT build. Inner build uses isolated LRM solely, but for resolution purposes > still is able to resolve from outer LRM, where outer build might deployed > artifacts, plugins used by IT inner build. > Technical remark: CLRM defines "head" LRM, and list of LRM as "tail". Almost > all methods are delegated toward "head", except for find methods (metadata > and artifact), exposing tail LRM contents for artifact resolution. Also, CLRM > is *able* to enforce artifact availability (as explained above), but in most > cases (at least in IT user story), one would want to inhibit this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7608) Make Resolver native transport the default in Maven4
[ https://issues.apache.org/jira/browse/MNG-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642609#comment-17642609 ] Hudson commented on MNG-7608: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-890 #3 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-890/3/ > Make Resolver native transport the default in Maven4 > > > Key: MNG-7608 > URL: https://issues.apache.org/jira/browse/MNG-7608 > Project: Maven > Issue Type: Improvement >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.x-candidate, 4.0.0 > > > The ancient Wagon should be phased out, and "native" resolver transport > should be the default in Maven4. This in start halves the HTTP request count > toward Maven Central and any major MRM. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7612) Chained Local Repository
[ https://issues.apache.org/jira/browse/MNG-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642608#comment-17642608 ] Hudson commented on MNG-7612: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-890 #3 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-890/3/ > Chained Local Repository > - > > Key: MNG-7612 > URL: https://issues.apache.org/jira/browse/MNG-7612 > Project: Maven > Issue Type: New Feature > Components: Artifacts and Repositories >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > New feature: Chained Local Repository Manager (CLRM). > This new feature is not something one would use in production, is more > targeted to Integration Test isolation. > User story: ITs usually are run as part of Maven build – lets call it "outer > build" – that may build among other things, plugins and some artifacts needed > for the ITs. The ITs itself – let's call them "inner build" – should run in > isolated environment. > Problem: the "outer build" is usually affected by user environment > (settings.xml, use of MRM, and may use user own local repository unless > alternate specified) but also we do not want user MRM to be altered by IT > runs. The "inner build" on the other hand, may fail if use same LRM as "outer > build", as they are isolated, so they do not use settings.xml from the outer > build, may not use MRM and same remote repository IDs, and all these may lead > to mysterious "artifact not found" problems. Typically, outer build may use > MRM that defines mirrorOf with ID "my-mrm", while inner would use defaults, > where only remote repository is "central": this leads that user LRM gets > populated with artifacts available from "my-mrm" remote repository, while > inner build would know only about "central" remote repository. Enhanced LRM > (default since Maven 3.0) would refuse to serve up these artifacts. > Solution is CLRM: with CLRM user is able to specify isolated LRM for ITs, > while still making artifacts from outer LRM "visible" (discoverable) for the > IT build. Inner build uses isolated LRM solely, but for resolution purposes > still is able to resolve from outer LRM, where outer build might deployed > artifacts, plugins used by IT inner build. > Technical remark: CLRM defines "head" LRM, and list of LRM as "tail". Almost > all methods are delegated toward "head", except for find methods (metadata > and artifact), exposing tail LRM contents for artifact resolution. Also, CLRM > is *able* to enforce artifact availability (as explained above), but in most > cases (at least in IT user story), one would want to inhibit this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7614) Maven should translate transport configuration fully to resolver transports.
[ https://issues.apache.org/jira/browse/MNG-7614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642607#comment-17642607 ] Hudson commented on MNG-7614: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-890 #3 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-890/3/ > Maven should translate transport configuration fully to resolver transports. > > > Key: MNG-7614 > URL: https://issues.apache.org/jira/browse/MNG-7614 > Project: Maven > Issue Type: Improvement >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0 > > > Maven should properly translate transport configuration, instead to assume > Wagon. > Master (Maven 4) got this fixed as part of MNG-7608, but for Maven 3.9.x this > needs to be backported, as it got native transporter as part of MNG-7454 but > confguration translation still needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7608) Make Resolver native transport the default in Maven4
[ https://issues.apache.org/jira/browse/MNG-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642594#comment-17642594 ] Hudson commented on MNG-7608: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #94 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/94/ > Make Resolver native transport the default in Maven4 > > > Key: MNG-7608 > URL: https://issues.apache.org/jira/browse/MNG-7608 > Project: Maven > Issue Type: Improvement >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.x-candidate, 4.0.0 > > > The ancient Wagon should be phased out, and "native" resolver transport > should be the default in Maven4. This in start halves the HTTP request count > toward Maven Central and any major MRM. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7614) Maven should translate transport configuration fully to resolver transports.
[ https://issues.apache.org/jira/browse/MNG-7614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642593#comment-17642593 ] Hudson commented on MNG-7614: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #94 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/94/ > Maven should translate transport configuration fully to resolver transports. > > > Key: MNG-7614 > URL: https://issues.apache.org/jira/browse/MNG-7614 > Project: Maven > Issue Type: Improvement >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0 > > > Maven should properly translate transport configuration, instead to assume > Wagon. > Master (Maven 4) got this fixed as part of MNG-7608, but for Maven 3.9.x this > needs to be backported, as it got native transporter as part of MNG-7454 but > confguration translation still needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7608) Make Resolver native transport the default in Maven4
[ https://issues.apache.org/jira/browse/MNG-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642585#comment-17642585 ] Hudson commented on MNG-7608: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #144 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/144/ > Make Resolver native transport the default in Maven4 > > > Key: MNG-7608 > URL: https://issues.apache.org/jira/browse/MNG-7608 > Project: Maven > Issue Type: Improvement >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.x-candidate, 4.0.0 > > > The ancient Wagon should be phased out, and "native" resolver transport > should be the default in Maven4. This in start halves the HTTP request count > toward Maven Central and any major MRM. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7617) Small optimisations and cleanup in the project/model building
[ https://issues.apache.org/jira/browse/MNG-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642568#comment-17642568 ] Hudson commented on MNG-7617: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #143 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/143/ > Small optimisations and cleanup in the project/model building > - > > Key: MNG-7617 > URL: https://issues.apache.org/jira/browse/MNG-7617 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 4.0.0-alpha-3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7616) Add missing exported artifacts for the new API
[ https://issues.apache.org/jira/browse/MNG-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642567#comment-17642567 ] Hudson commented on MNG-7616: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #143 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/143/ > Add missing exported artifacts for the new API > -- > > Key: MNG-7616 > URL: https://issues.apache.org/jira/browse/MNG-7616 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7613) Upgrade Apache Maven parent POM to version 38
[ https://issues.apache.org/jira/browse/MNG-7613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642521#comment-17642521 ] Hudson commented on MNG-7613: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #93 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/93/ > Upgrade Apache Maven parent POM to version 38 > - > > Key: MNG-7613 > URL: https://issues.apache.org/jira/browse/MNG-7613 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7613) Upgrade Apache Maven parent POM to version 38
[ https://issues.apache.org/jira/browse/MNG-7613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642478#comment-17642478 ] Hudson commented on MNG-7613: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #92 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/92/ > Upgrade Apache Maven parent POM to version 38 > - > > Key: MNG-7613 > URL: https://issues.apache.org/jira/browse/MNG-7613 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-6609) Profile activation by packaging
[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642479#comment-17642479 ] Hudson commented on MNG-6609: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #92 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/92/ > Profile activation by packaging > > > Key: MNG-6609 > URL: https://issues.apache.org/jira/browse/MNG-6609 > Project: Maven > Issue Type: Improvement > Components: Profiles >Affects Versions: 3.6.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > Due to the lack of mixins, it is common that modules which use different > packagings share the same parent pom. As those often use different > dependencies/plugins, it would be nice to have profiles which are activated > based on the packaging of a module. That is currently not possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7596) Upgrade to plexus-utils 3.5.0
[ https://issues.apache.org/jira/browse/MNG-7596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642181#comment-17642181 ] Hudson commented on MNG-7596: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #142 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/142/ > Upgrade to plexus-utils 3.5.0 > - > > Key: MNG-7596 > URL: https://issues.apache.org/jira/browse/MNG-7596 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-6609) Profile activation by packaging
[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642180#comment-17642180 ] Hudson commented on MNG-6609: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #141 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/141/ > Profile activation by packaging > > > Key: MNG-6609 > URL: https://issues.apache.org/jira/browse/MNG-6609 > Project: Maven > Issue Type: Improvement > Components: Profiles >Affects Versions: 3.6.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > Due to the lack of mixins, it is common that modules which use different > packagings share the same parent pom. As those often use different > dependencies/plugins, it would be nice to have profiles which are activated > based on the packaging of a module. That is currently not possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7611) java.lang.IllegalStateException: Required Java version 1.8 is not met by current version: 17.0.5
[
https://issues.apache.org/jira/browse/MNG-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642179#comment-17642179
]
Hudson commented on MNG-7611:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #141
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/141/
> java.lang.IllegalStateException: Required Java version 1.8 is not met by
> current version: 17.0.5
>
>
> Key: MNG-7611
> URL: https://issues.apache.org/jira/browse/MNG-7611
> Project: Maven
> Issue Type: Task
>Reporter: Guillaume Nodet
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 4.0.0-alpha-3
>
>
> {code:java}
> Caused by: java.lang.IllegalStateException: Required Java version 1.8 is not
> met by current version: 17.0.5
>at
> org.apache.maven.plugin.internal.MavenPluginJavaPrerequisiteChecker.accept(MavenPluginJavaPrerequisiteChecker.java:38)
>at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.lambda$checkPrerequisites$1(DefaultMavenPluginManager.java:289)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-6609) Profile activation by packaging
[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641913#comment-17641913 ] Hudson commented on MNG-6609: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #140 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/140/ > Profile activation by packaging > > > Key: MNG-6609 > URL: https://issues.apache.org/jira/browse/MNG-6609 > Project: Maven > Issue Type: Improvement > Components: Profiles >Affects Versions: 3.6.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > Due to the lack of mixins, it is common that modules which use different > packagings share the same parent pom. As those often use different > dependencies/plugins, it would be nice to have profiles which are activated > based on the packaging of a module. That is currently not possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7606) Maven 3.9.0-SNAPSHOT cannot build Maven 4.0.0-SNAPSHOT
[
https://issues.apache.org/jira/browse/MNG-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641914#comment-17641914
]
Hudson commented on MNG-7606:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #140
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/140/
> Maven 3.9.0-SNAPSHOT cannot build Maven 4.0.0-SNAPSHOT
> --
>
> Key: MNG-7606
> URL: https://issues.apache.org/jira/browse/MNG-7606
> Project: Maven
> Issue Type: Bug
>Reporter: Tamas Cservenak
>Assignee: Konrad Windszus
>Priority: Blocker
> Fix For: 3.9.0
>
>
> How to reproduce: build maven-3.9.x branch
> (e921f1564ef9460ca58745eb52e3967dbbd0b9e7) then checkout master branch
> (c6ecff9923088d854d4621e17d602f1c70dda806) and try to build it with built
> 3.9.0-SNAPSHOT: it fails.
> Error is:
> {noformat}
> [cstamas@blondie maven (master)]$ mvn -V clean install
> Apache Maven 3.9.0-SNAPSHOT (e921f1564ef9460ca58745eb52e3967dbbd0b9e7)
> Maven home: /home/cstamas/.sdkman/candidates/maven/3.9.0-SNAPSHOT
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> /home/cstamas/.sdkman/candidates/java/17.0.5-tem
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "6.0.9-300.fc37.x86_64", arch: "amd64", family:
> "unix"
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [ERROR] 'dependencies.dependency.version' for
> org.junit.jupiter:junit-jupiter-engine:jar is missing. @ line 485, column 17
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project org.apache.maven:maven:4.0.0-alpha-3-SNAPSHOT
> (/home/cstamas/Worx/apache-maven/maven/pom.xml) has 1 error
> [ERROR] 'dependencies.dependency.version' for
> org.junit.jupiter:junit-jupiter-engine:jar is missing. @ line 485, column 17
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [cstamas@blondie maven (master)]$ {noformat}
> Maven 3.8.6 and 4.0.0-alpha-3-SNAPSHOT builds master just fine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7607) Add Transport to new Immutable API
[ https://issues.apache.org/jira/browse/MNG-7607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641912#comment-17641912 ] Hudson commented on MNG-7607: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #140 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/140/ > Add Transport to new Immutable API > -- > > Key: MNG-7607 > URL: https://issues.apache.org/jira/browse/MNG-7607 > Project: Maven > Issue Type: New Feature >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.x-candidate, 4.0.0 > > > Introduce simple API to GET/PUT resources. Keep it intentionally simple, that > still covers quite broad range of use cases. If plugin/extension needs a bit > advanced features (like conditional GETs or whatnot), they should roll their > own. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7606) Maven 3.9.0-SNAPSHOT cannot build Maven 4.0.0-SNAPSHOT
[
https://issues.apache.org/jira/browse/MNG-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641879#comment-17641879
]
Hudson commented on MNG-7606:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #91
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/91/
> Maven 3.9.0-SNAPSHOT cannot build Maven 4.0.0-SNAPSHOT
> --
>
> Key: MNG-7606
> URL: https://issues.apache.org/jira/browse/MNG-7606
> Project: Maven
> Issue Type: Bug
>Reporter: Tamas Cservenak
>Assignee: Konrad Windszus
>Priority: Blocker
> Fix For: 3.9.0
>
>
> How to reproduce: build maven-3.9.x branch
> (e921f1564ef9460ca58745eb52e3967dbbd0b9e7) then checkout master branch
> (c6ecff9923088d854d4621e17d602f1c70dda806) and try to build it with built
> 3.9.0-SNAPSHOT: it fails.
> Error is:
> {noformat}
> [cstamas@blondie maven (master)]$ mvn -V clean install
> Apache Maven 3.9.0-SNAPSHOT (e921f1564ef9460ca58745eb52e3967dbbd0b9e7)
> Maven home: /home/cstamas/.sdkman/candidates/maven/3.9.0-SNAPSHOT
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> /home/cstamas/.sdkman/candidates/java/17.0.5-tem
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "6.0.9-300.fc37.x86_64", arch: "amd64", family:
> "unix"
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [ERROR] 'dependencies.dependency.version' for
> org.junit.jupiter:junit-jupiter-engine:jar is missing. @ line 485, column 17
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project org.apache.maven:maven:4.0.0-alpha-3-SNAPSHOT
> (/home/cstamas/Worx/apache-maven/maven/pom.xml) has 1 error
> [ERROR] 'dependencies.dependency.version' for
> org.junit.jupiter:junit-jupiter-engine:jar is missing. @ line 485, column 17
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [cstamas@blondie maven (master)]$ {noformat}
> Maven 3.8.6 and 4.0.0-alpha-3-SNAPSHOT builds master just fine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-6609) Profile activation by packaging
[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641878#comment-17641878 ] Hudson commented on MNG-6609: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #91 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/91/ > Profile activation by packaging > > > Key: MNG-6609 > URL: https://issues.apache.org/jira/browse/MNG-6609 > Project: Maven > Issue Type: Improvement > Components: Profiles >Affects Versions: 3.6.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > Due to the lack of mixins, it is common that modules which use different > packagings share the same parent pom. As those often use different > dependencies/plugins, it would be nice to have profiles which are activated > based on the packaging of a module. That is currently not possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-837) Upgrade Parent to 38
[ https://issues.apache.org/jira/browse/MDEP-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641587#comment-17641587 ] Hudson commented on MDEP-837: - Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin » master #70 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/master/70/ > Upgrade Parent to 38 > > > Key: MDEP-837 > URL: https://issues.apache.org/jira/browse/MDEP-837 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: version-next > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-371) Fix checkstyle configuration
[ https://issues.apache.org/jira/browse/MPOM-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641578#comment-17641578 ] Hudson commented on MPOM-371: - Build succeeded in Jenkins: Maven » Maven TLP » maven-parent » master #67 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-parent/job/master/67/ > Fix checkstyle configuration > > > Key: MPOM-371 > URL: https://issues.apache.org/jira/browse/MPOM-371 > Project: Maven POMs > Issue Type: Bug > Components: maven >Affects Versions: MAVEN-38 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Critical > Fix For: MAVEN-39 > > > We have new checkstyle configuration in shared-resource but old one is used. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-837) Upgrade Parent to 38
[ https://issues.apache.org/jira/browse/MDEP-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641577#comment-17641577 ] Hudson commented on MDEP-837: - Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin » master #69 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/master/69/ > Upgrade Parent to 38 > > > Key: MDEP-837 > URL: https://issues.apache.org/jira/browse/MDEP-837 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: version-next > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-446) ERROR during build of m-plugin-report-p and m-plugin-p: Dependencies in wrong scope
[
https://issues.apache.org/jira/browse/MPLUGIN-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641556#comment-17641556
]
Hudson commented on MPLUGIN-446:
Build succeeded in Jenkins: Maven » Maven TLP » maven-plugin-tools » master #90
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-tools/job/master/90/
> ERROR during build of m-plugin-report-p and m-plugin-p: Dependencies in wrong
> scope
> ---
>
> Key: MPLUGIN-446
> URL: https://issues.apache.org/jira/browse/MPLUGIN-446
> Project: Maven Plugin Tools
> Issue Type: Bug
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.8.0
>
>
> The following errors can be observed during the build of the current master
> since MPLUGIN-441
> {code}
> [INFO] --- maven-plugin-plugin:3.6.4:descriptor (default-descriptor) @
> maven-plugin-plugin ---
> [ERROR]
> Some dependencies of Maven Plugins are expected to be in provided scope.
> Please make sure that dependencies listed below declared in POM
> have set 'provided' as well.
> The following dependencies are in wrong scope:
> * org.apache.maven:plexus-utils:jar:4.0.0-alpha-2:compile
> [INFO] Using 'UTF-8' encoding to read mojo source files.
> [INFO] java-annotations mojo extractor found 5 mojo descriptors.
> {code}
> This is emitted 4 times (for both goals descriptor and help-mojo in modules
> m-plugin-report-p and m-plugin-p).
> In addition {{plexus-utils}} is now twice in the dependency hierarchy:
> - Directly referenced with group id {{o.a.m}}
> - Transitively referenced with group id {{org.codehaus.plexus}}, e.g. from
> {{maven-core}}.
> As they cannot really coexist in the same classloader (as both export at
> least partially the same package names) only one version should ever be
> used
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-425) Plugin descriptor should contain the requiredJavaVersion/requiredMavenVersion
[ https://issues.apache.org/jira/browse/MPLUGIN-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641555#comment-17641555 ] Hudson commented on MPLUGIN-425: Build succeeded in Jenkins: Maven » Maven TLP » maven-plugin-tools » master #90 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-tools/job/master/90/ > Plugin descriptor should contain the requiredJavaVersion/requiredMavenVersion > - > > Key: MPLUGIN-425 > URL: https://issues.apache.org/jira/browse/MPLUGIN-425 > Project: Maven Plugin Tools > Issue Type: Improvement > Components: Plugin Plugin >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: next-release > > > As plugin descriptor schema v 1.1.0 supports requiring a Java version > (support added in MNG-7566) and Maven version (support added in MNG-7570), > the descriptor goal provide a dedicated mojo parameter to set these elements. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGINTESTING-78) Support the new maven 4 api
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641308#comment-17641308 ] Hudson commented on MPLUGINTESTING-78: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-plugin-testing » master #25 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-testing/job/master/25/ > Support the new maven 4 api > --- > > Key: MPLUGINTESTING-78 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-78 > Project: Maven Plugin Testing > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-918) Upgrade Maven Reporting API to 4.0.0-M3
[ https://issues.apache.org/jira/browse/MSITE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641203#comment-17641203 ] Hudson commented on MSITE-918: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #49 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/49/ > Upgrade Maven Reporting API to 4.0.0-M3 > --- > > Key: MSITE-918 > URL: https://issues.apache.org/jira/browse/MSITE-918 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-915) Upgrade Plexus Utils to 3.5.0
[ https://issues.apache.org/jira/browse/MSITE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641193#comment-17641193 ] Hudson commented on MSITE-915: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #48 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/48/ > Upgrade Plexus Utils to 3.5.0 > - > > Key: MSITE-915 > URL: https://issues.apache.org/jira/browse/MSITE-915 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-916) Upgrade Plexus Archiver to 4.6.0
[ https://issues.apache.org/jira/browse/MSITE-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641192#comment-17641192 ] Hudson commented on MSITE-916: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #48 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/48/ > Upgrade Plexus Archiver to 4.6.0 > > > Key: MSITE-916 > URL: https://issues.apache.org/jira/browse/MSITE-916 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-370) Document "format" profile
[
https://issues.apache.org/jira/browse/MPOM-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641181#comment-17641181
]
Hudson commented on MPOM-370:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-parent » master #66
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-parent/job/master/66/
> Document "format" profile
> -
>
> Key: MPOM-370
> URL: https://issues.apache.org/jira/browse/MPOM-370
> Project: Maven POMs
> Issue Type: Improvement
> Components: maven
>Affects Versions: MAVEN-38
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: MAVEN-39
>
>
> Currently the new "format" profile introduced with MPOM-349 is not documented
> at https://maven.apache.org/pom/maven/
> (https://github.com/apache/maven-parent/blob/master/src/site-docs/apt/index.apt.vm).
> It should be briefly explained there. Also a good reference with an
> explanation of the {{.git-blame-ignore-revs}} file name and format should be
> added (unfortunately https://git-scm.com/docs/git-blame does not mention that
> standard filename)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNGSITE-500) Update "Code Style And Code Conventions" page with automatic spotless formatting
[ https://issues.apache.org/jira/browse/MNGSITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641176#comment-17641176 ] Hudson commented on MNGSITE-500: Build succeeded in Jenkins: Maven » Maven TLP » maven-site » master #177 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site/job/master/177/ > Update "Code Style And Code Conventions" page with automatic spotless > formatting > > > Key: MNGSITE-500 > URL: https://issues.apache.org/jira/browse/MNGSITE-500 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Konrad Windszus >Priority: Major > > With https://issues.apache.org/jira/browse/MPOM-349 the coding conventions > changed as well. The page at > https://maven.apache.org/developers/conventions/code.html needs an update to > reflect this change. > This will probably also resolve > * MNGSITE-469 > * MNGSITE-480 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGINTESTING-78) Support the new maven 4 api
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641159#comment-17641159 ] Hudson commented on MPLUGINTESTING-78: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-plugin-testing » master #24 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-testing/job/master/24/ > Support the new maven 4 api > --- > > Key: MPLUGINTESTING-78 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-78 > Project: Maven Plugin Testing > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-913) Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4
[ https://issues.apache.org/jira/browse/MSITE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640980#comment-17640980 ] Hudson commented on MSITE-913: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #47 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/47/ > Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4 > > > Key: MSITE-913 > URL: https://issues.apache.org/jira/browse/MSITE-913 > Project: Maven Site Plugin > Issue Type: Dependency upgrade > Components: doxia integration >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1164) Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4
[ https://issues.apache.org/jira/browse/MSHARED-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640949#comment-17640949 ] Hudson commented on MSHARED-1164: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-exec » master #31 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-exec/job/master/31/ > Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4 > > > Key: MSHARED-1164 > URL: https://issues.apache.org/jira/browse/MSHARED-1164 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1160) Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4
[ https://issues.apache.org/jira/browse/MSHARED-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640948#comment-17640948 ] Hudson commented on MSHARED-1160: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-impl » master #36 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-impl/job/master/36/ > Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4 > > > Key: MSHARED-1160 > URL: https://issues.apache.org/jira/browse/MSHARED-1160 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINDEXER-181) IndexDataReader should use Sets instead of ConcurrentHashMaps w/ fixed values
[
https://issues.apache.org/jira/browse/MINDEXER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640013#comment-17640013
]
Hudson commented on MINDEXER-181:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #86
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/86/
> IndexDataReader should use Sets instead of ConcurrentHashMaps w/ fixed values
> -
>
> Key: MINDEXER-181
> URL: https://issues.apache.org/jira/browse/MINDEXER-181
> Project: Maven Indexer
> Issue Type: Improvement
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 7.0.1
>
>
> Noticed that both, the single threaded and the multi threaded impl used CHMs.
> Instead of only changing {{readIndexST}} to plain {{{}Map{}}}s, I switched
> everything to {{{}Set{}}}s.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-6609) Profile activation by packaging
[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639915#comment-17639915 ] Hudson commented on MNG-6609: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #90 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/90/ > Profile activation by packaging > > > Key: MNG-6609 > URL: https://issues.apache.org/jira/browse/MNG-6609 > Project: Maven > Issue Type: Improvement > Components: Profiles >Affects Versions: 3.6.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > Due to the lack of mixins, it is common that modules which use different > packagings share the same parent pom. As those often use different > dependencies/plugins, it would be nice to have profiles which are activated > based on the packaging of a module. That is currently not possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-6609) Profile activation by packaging
[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639872#comment-17639872 ] Hudson commented on MNG-6609: - Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #89 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/89/ > Profile activation by packaging > > > Key: MNG-6609 > URL: https://issues.apache.org/jira/browse/MNG-6609 > Project: Maven > Issue Type: Improvement > Components: Profiles >Affects Versions: 3.6.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > Due to the lack of mixins, it is common that modules which use different > packagings share the same parent pom. As those often use different > dependencies/plugins, it would be nice to have profiles which are activated > based on the packaging of a module. That is currently not possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINDEXER-180) Upgrade to Maven Resolver 1.9.2
[ https://issues.apache.org/jira/browse/MINDEXER-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639836#comment-17639836 ] Hudson commented on MINDEXER-180: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #85 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/85/ > Upgrade to Maven Resolver 1.9.2 > --- > > Key: MINDEXER-180 > URL: https://issues.apache.org/jira/browse/MINDEXER-180 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.0.1 > > > Bump resolver to 1.9.2 (was 1.8.2). Resolver is used only to parse versions > (so api and util is being used). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINDEXER-175) Examples does not need to be deployed
[ https://issues.apache.org/jira/browse/MINDEXER-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639834#comment-17639834 ] Hudson commented on MINDEXER-175: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #83 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/83/ > Examples does not need to be deployed > - > > Key: MINDEXER-175 > URL: https://issues.apache.org/jira/browse/MINDEXER-175 > Project: Maven Indexer > Issue Type: Task >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.0.1 > > > They are really just showcase and deploying them is a waste of bytes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINDEXER-176) Core's IndexDataReader does not clean up after itself
[ https://issues.apache.org/jira/browse/MINDEXER-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639832#comment-17639832 ] Hudson commented on MINDEXER-176: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #82 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/82/ > Core's IndexDataReader does not clean up after itself > - > > Key: MINDEXER-176 > URL: https://issues.apache.org/jira/browse/MINDEXER-176 > Project: Maven Indexer > Issue Type: Bug >Affects Versions: 7.0.0 >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.0.1 > > > As MT index update was implemented that uses split "silos", it seems that > silos are not cleaned up. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINDEXER-179) Update install/deploy plugins to latest
[ https://issues.apache.org/jira/browse/MINDEXER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639833#comment-17639833 ] Hudson commented on MINDEXER-179: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #84 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/84/ > Update install/deploy plugins to latest > --- > > Key: MINDEXER-179 > URL: https://issues.apache.org/jira/browse/MINDEXER-179 > Project: Maven Indexer > Issue Type: Task >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.0.1 > > > Changes: > * m-install-p 3.1.0 > * m-deploy-p 3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-6609) Profile activation by packaging
[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639677#comment-17639677 ] Hudson commented on MNG-6609: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #88 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/88/ > Profile activation by packaging > > > Key: MNG-6609 > URL: https://issues.apache.org/jira/browse/MNG-6609 > Project: Maven > Issue Type: Improvement > Components: Profiles >Affects Versions: 3.6.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3 > > > Due to the lack of mixins, it is common that modules which use different > packagings share the same parent pom. As those often use different > dependencies/plugins, it would be nice to have profiles which are activated > based on the packaging of a module. That is currently not possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7561) DefaultVersionRangeResolver should not try to resolve versions with same upper and lower bound
[
https://issues.apache.org/jira/browse/MNG-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639641#comment-17639641
]
Hudson commented on MNG-7561:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #87
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/87/
> DefaultVersionRangeResolver should not try to resolve versions with same
> upper and lower bound
> --
>
> Key: MNG-7561
> URL: https://issues.apache.org/jira/browse/MNG-7561
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3
>
>
> For dependencies having e.g. version {{[1.0]}} the
> DefaultVersionRangeResolver still tries to resolve versions although only a
> single version (namely 1.0) is valid here according to
> https://maven.apache.org/pom.html#Dependency_Version_Requirement_Specification.
>
> This leads in the worst case to long-running calls against a remote
> repository for no reason.
> There should be a shortcut in
> https://github.com/apache/maven/blob/3f90e7028e0338c110aea267b44362653d55273a/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java#L108
> when the range has the same upper and lower bound.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639549#comment-17639549 ] Hudson commented on MNG-7586: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #139 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/139/ > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639547#comment-17639547 ] Hudson commented on MNG-7586: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #86 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/86/ > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1165) Upgrade plugins and components in ITs
[ https://issues.apache.org/jira/browse/MSHARED-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639330#comment-17639330 ] Hudson commented on MSHARED-1165: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-impl » master #35 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-impl/job/master/35/ > Upgrade plugins and components in ITs > - > > Key: MSHARED-1165 > URL: https://issues.apache.org/jira/browse/MSHARED-1165 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0-M3 > > > * Upgrade Maven Install Plugin to 3.1.0 > * Upgrade Maven Site Plugin to 4.0.0-M3 > * Upgrade Maven Project Info Reports Plugin to 3.4.1 > * Upgrade Maven Reporting API to 4.0.0-M3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1167) Upgrade plugins in ITs
[ https://issues.apache.org/jira/browse/MSHARED-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639288#comment-17639288 ] Hudson commented on MSHARED-1167: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-exec » master #30 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-exec/job/master/30/ > Upgrade plugins in ITs > -- > > Key: MSHARED-1167 > URL: https://issues.apache.org/jira/browse/MSHARED-1167 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0-M3 > > > * Upgrade Maven Site Plugin to 4.0.0-M3 > * Upgrade Maven Project Info Reports Plugin to 3.4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1166) Upgrade Plexus Utils to 3.5.0
[ https://issues.apache.org/jira/browse/MSHARED-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639263#comment-17639263 ] Hudson commented on MSHARED-1166: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-exec » master #29 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-exec/job/master/29/ > Upgrade Plexus Utils to 3.5.0 > - > > Key: MSHARED-1166 > URL: https://issues.apache.org/jira/browse/MSHARED-1166 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1163) Upgrade Maven Reporting API to 4.0.0-M3
[ https://issues.apache.org/jira/browse/MSHARED-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639264#comment-17639264 ] Hudson commented on MSHARED-1163: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-exec » master #29 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-exec/job/master/29/ > Upgrade Maven Reporting API to 4.0.0-M3 > --- > > Key: MSHARED-1163 > URL: https://issues.apache.org/jira/browse/MSHARED-1163 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638859#comment-17638859 ] Hudson commented on MCLEAN-103: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-clean-plugin » master #26 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-clean-plugin/job/master/26/ > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638856#comment-17638856 ] Hudson commented on MENFORCER-438: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-enforcer » master #80 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/80/ > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MASSEMBLY-941) file permissions removed during assembly:single since 3.2.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638844#comment-17638844 ] Hudson commented on MASSEMBLY-941: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-assembly-plugin » master #37 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-assembly-plugin/job/master/37/ > file permissions removed during assembly:single since 3.2.0 > --- > > Key: MASSEMBLY-941 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-941 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: permissions >Affects Versions: 3.2.0, 3.3.0 >Reporter: Christopher Tubbs >Assignee: Herve Boutemy >Priority: Critical > Fix For: next-release > > > Since 3.2.0, existing file permissions seem to be ignored when creating a > tarball assembly, and files stored in the assembly do not have their original > file permissions preserved. > Using version 3.1.1 of this plugin and earlier, when creating a tar.gz, > existing file permissions are normally preserved. This is now broken in > 3.2.0, unless the component descriptor explicitly sets the fileModes. > This was discovered trying to prepare a release candidate for Apache Accumulo > using the apache-23.pom parent POM's predefined `source-release-tar` > descriptor using the `single` goal. We noticed that the resulting > source-release tarball had stripped all the executable permissions from our > scripts, instead of preserving them. This makes the resulting source release > more difficult to build from source. > A source-release assembly, and any other assembly that does not specify the > file permissions explicitly, should preserve the existing file permissions, > just as it used to with 3.1.1 and earlier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-358) Upgrade to PMD 6.52.0
[ https://issues.apache.org/jira/browse/MPMD-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638841#comment-17638841 ] Hudson commented on MPMD-358: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pmd-plugin » master #70 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/70/ > Upgrade to PMD 6.52.0 > - > > Key: MPMD-358 > URL: https://issues.apache.org/jira/browse/MPMD-358 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
