[jira] [Commented] (MNG-7464) Warn about using read-only parameters for Mojo in configuration
[ https://issues.apache.org/jira/browse/MNG-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532496#comment-17532496 ] Hudson commented on MNG-7464: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #41 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/41/ > Warn about using read-only parameters for Mojo in configuration > --- > > Key: MNG-7464 > URL: https://issues.apache.org/jira/browse/MNG-7464 > Project: Maven > Issue Type: New Feature >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MRESOLVER-256) Dependency tree is different between DF and BF strategies when a dependency package has no indirect dependencies
[ https://issues.apache.org/jira/browse/MRESOLVER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532477#comment-17532477 ] Hudson commented on MRESOLVER-256: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #29 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/29/ > Dependency tree is different between DF and BF strategies when a dependency > package has no indirect dependencies > > > Key: MRESOLVER-256 > URL: https://issues.apache.org/jira/browse/MRESOLVER-256 > Project: Maven Resolver > Issue Type: Bug > Components: Resolver >Affects Versions: 1.8.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.8.1 > > > From GitHub: > Fix the problem that the dependency tree is different when DF and BF > strategies are adopted when a dependency package has no children dependency. > When BF is adopted, when a dependent package has no children dependency, it > will not continue to call the doRecurse() method, that is, it will not call > the CacheManager.cachewinner() to put this dependency package into the > winnerGAs object, which affects the analysis results of dependency packages > of the same GA. The current fix is to call the CacheManager.cachewinner() > method when a dependent package has no children dependency and it is not skip > resolution, so that the dependent package can be found in winnerGAs. > We take the dependency in the following figure as an example to illustrate > the generation process of the problem. > src="https://user-images.githubusercontent.com/104960983/166911972-6d721f62-ea17-46fc-af60-181aa5fdb041.png;> > At org eclipse. aether. internal. impl. Bfdependencycollector > #collectdependencies() mainly has two stages: processdependency() and > transformer.transformGraph( node, context )。 > In the first stage of process dependency: > 1. When parsing to D1, descriptorResult.getDependencies().isEmpty(), so > doRecurse() will not be executed. Therefore, args.skipper.cache() will not be > executed. The D1 will not exist in winnerGAs in the end. >  > 2. When parsing D2 of the same layer, because there is no same GA in > winnerGAs, D2 and its children dependencies （ G1 and H1） will be parsed. > 3. When resolving to G2 on the same layer as G1, because winnerGAs already > has G1, the resolution of the children dependencies of G2 will be skipped, > that is, H2 will not be resolved. > Then, to the second stage, transformgraph: > 4. Because D1 has the same depth as D2, D1 wins, that is, D2 and its children > are eliminated, including G1 > 5. Because G1 was eliminated, G2 won. > Finally, the final dependency tree obtained by BF strategy is as follows: > src="https://user-images.githubusercontent.com/104960983/166912027-21d7fcd4-79bd-43cc-80c8-0088091a91ef.png;> > But the dependency tree obtained by DF is as follows: > src="https://user-images.githubusercontent.com/104960983/166912045-2cff5bd6-f54d-4faa-a955-6c985923058a.png;> > That is, in the final generated dependency tree, BF has less children > dependency of G2 than DF. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7464) Warn about using read-only parameters for Mojo in configuration
[ https://issues.apache.org/jira/browse/MNG-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531872#comment-17531872 ] Hudson commented on MNG-7464: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-731 #5 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-731/5/ > Warn about using read-only parameters for Mojo in configuration > --- > > Key: MNG-7464 > URL: https://issues.apache.org/jira/browse/MNG-7464 > Project: Maven > Issue Type: New Feature >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSHARED-1068) Upgrade Groovy to 4.0.2
[ https://issues.apache.org/jira/browse/MSHARED-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531418#comment-17531418 ] Hudson commented on MSHARED-1068: - Build succeeded in Jenkins: Maven » Maven TLP » maven-script-interpreter » master #13 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-script-interpreter/job/master/13/ > Upgrade Groovy to 4.0.2 > --- > > Key: MSHARED-1068 > URL: https://issues.apache.org/jira/browse/MSHARED-1068 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-script-interpreter >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: maven-script-interpreter-1.3 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSHARED-1002) Require Java 8
[ https://issues.apache.org/jira/browse/MSHARED-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531415#comment-17531415 ] Hudson commented on MSHARED-1002: - Build succeeded in Jenkins: Maven » Maven TLP » maven-script-interpreter » master #12 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-script-interpreter/job/master/12/ > Require Java 8 > -- > > Key: MSHARED-1002 > URL: https://issues.apache.org/jira/browse/MSHARED-1002 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-common-artifact-filters, maven-filtering, > maven-script-interpreter >Reporter: Sylwester Lachiewicz >Priority: Major > Fix For: maven-script-interpreter-1.3 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MTOOLCHAINS-31) Not threadsafe for parallel execution
[
https://issues.apache.org/jira/browse/MTOOLCHAINS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530765#comment-17530765
]
Hudson commented on MTOOLCHAINS-31:
---
Build succeeded in Jenkins: Maven » Maven TLP » maven-toolchains-plugin »
master #6
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-toolchains-plugin/job/master/6/
> Not threadsafe for parallel execution
> -
>
> Key: MTOOLCHAINS-31
> URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-31
> Project: Maven Toolchains Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
> Environment: maven 3.6.1
>Reporter: Hüseyin Kartal
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.0.1
>
>
> Running maven in parallel mode result in following output which also includes
> TOOLCHAINS plugin.
> {noformat}
> *
> * Your build is requesting parallel execution, but project *
> * contains the following plugin(s) that have goals not marked *
> * as @threadSafe to support parallel building. *
> * While this /may/ work fine, please look for plugin updates*
> * and/or request plugins be made thread-safe. *
> * If reporting an issue, report it against the plugin in*
> * question, not against maven-core *
> *
> The following plugins are not marked @threadSafe in Application component:
> core:
> com.sun.xml.ws:jaxws-maven-plugin:2.3.2
> org.apache.maven.plugins:maven-jxr-plugin:3.0.0
> org.apache.maven.plugins:maven-toolchains-plugin:3.0.0
> Enable debug to see more precisely which goals are not marked @threadSafe.
> *{noformat}
> Toolchains plugin should made and/or marked threadSafe.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MINDEXER-121) ChunkReaderIterator leaks InputStreams
[ https://issues.apache.org/jira/browse/MINDEXER-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530708#comment-17530708 ] Hudson commented on MINDEXER-121: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #31 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/31/ > ChunkReaderIterator leaks InputStreams > -- > > Key: MINDEXER-121 > URL: https://issues.apache.org/jira/browse/MINDEXER-121 > Project: Maven Indexer > Issue Type: Bug >Reporter: Stephen Buergler >Assignee: Tamás Cservenák >Priority: Minor > Fix For: 6.2.0 > > > ChunkReaderIterator closes ChunkReaders when you call next(). The last > ChunkReader never gets closed because next() doesn't get called after the > last element has been returned. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MASSEMBLY-954) Update plugin (requires Maven 3.2.5+)
[ https://issues.apache.org/jira/browse/MASSEMBLY-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530647#comment-17530647 ] Hudson commented on MASSEMBLY-954: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-assembly-plugin » master #6 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-assembly-plugin/job/master/6/ > Update plugin (requires Maven 3.2.5+) > - > > Key: MASSEMBLY-954 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-954 > Project: Maven Assembly Plugin > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.3.1 > > > Update plugin source and dependencies: > * update Maven requirement to 3.2.5+ > * set maven bits to provided > * drop legacy dependencies, use current ones -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSKINS-172) Non-deliberate margin between navigation and rest in side bar
[
https://issues.apache.org/jira/browse/MSKINS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530471#comment-17530471
]
Hudson commented on MSKINS-172:
---
Build succeeded in Jenkins: Maven » Maven TLP » maven-fluido-skin » master #10
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-fluido-skin/job/master/10/
> Non-deliberate margin between navigation and rest in side bar
> -
>
> Key: MSKINS-172
> URL: https://issues.apache.org/jira/browse/MSKINS-172
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-1.8
>Reporter: Konrad Windszus
>Assignee: Michael Osipov
>Priority: Major
> Fix For: fluido-1.11.0
>
> Attachments: fluido-1.7.png, fluido-1.9.png
>
>
> Due to the change
> https://github.com/apache/maven-fluido-skin/commit/f9cbe82ff307c61cefe0336da89eb0082086585a#diff-f1940cd019654c7f2cb1801363b96b62c6526752fa8640c8de042ea4f0f36778R226
> introduced with MSKINS-153 there is a margin between the navigation and the
> google site search bar and the powered by section. For example look at
> https://jackrabbit.apache.org/filevault-package-maven-plugin/index.html.
> This is caused by the markup change from
> {code}
>
> ...menu, search bar and powered by
>
> {code} to
> {code}
>
> ...menu
>
>
> ...search bar and powered by
>
> {code}
> combined with the CSS for class {{sidebar-nav}}:
> https://github.com/apache/maven-fluido-skin/blob/0cef65c2abd91af3297b2e7ec95790e7b4bfabb0/src/main/resources/css/maven-theme.css#L126
> Example site leveraging fluido 1.9
> (https://jackrabbit.apache.org/filevault-package-maven-plugin/index.html):
> !fluido-1.9.png!
> Example site leveraging fluido 1.7
> (https://maven.apache.org/plugins/maven-compiler-plugin/index.html referenced
> in
> https://github.com/apache/maven-parent/blob/maven-parent-34/src/site/site.xml#L39):
> !fluido-1.7.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MSKINS-179) Upgrade plugins ITs
[ https://issues.apache.org/jira/browse/MSKINS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530468#comment-17530468 ] Hudson commented on MSKINS-179: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-fluido-skin » master #10 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-fluido-skin/job/master/10/ > Upgrade plugins ITs > --- > > Key: MSKINS-179 > URL: https://issues.apache.org/jira/browse/MSKINS-179 > Project: Maven Skins > Issue Type: Dependency upgrade > Components: Fluido Skin >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: fluido-1.11.0 > > > * Maven Site Plugin to 3.12.0 > * Maven Project Info Reports Plugin 3.12.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSKINS-181) Replace deprecated Velocity context parameters
[ https://issues.apache.org/jira/browse/MSKINS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530470#comment-17530470 ] Hudson commented on MSKINS-181: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-fluido-skin » master #10 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-fluido-skin/job/master/10/ > Replace deprecated Velocity context parameters > -- > > Key: MSKINS-181 > URL: https://issues.apache.org/jira/browse/MSKINS-181 > Project: Maven Skins > Issue Type: Task > Components: Fluido Skin >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: fluido-1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSKINS-182) Fix padding of search input form
[ https://issues.apache.org/jira/browse/MSKINS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530472#comment-17530472 ] Hudson commented on MSKINS-182: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-fluido-skin » master #10 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-fluido-skin/job/master/10/ > Fix padding of search input form > > > Key: MSKINS-182 > URL: https://issues.apache.org/jira/browse/MSKINS-182 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.10.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Attachments: screenshot-1.png > > > The padding is currently out of bounds: > !screenshot-1.png! > Make the search input form inside the bounds of the div element. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSKINS-180) Raise Doxia Sitetools prerequisite to 1.11.1
[ https://issues.apache.org/jira/browse/MSKINS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530469#comment-17530469 ] Hudson commented on MSKINS-180: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-fluido-skin » master #10 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-fluido-skin/job/master/10/ > Raise Doxia Sitetools prerequisite to 1.11.1 > > > Key: MSKINS-180 > URL: https://issues.apache.org/jira/browse/MSKINS-180 > Project: Maven Skins > Issue Type: Task > Components: Fluido Skin >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: fluido-1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSKINS-178) Upgrade Parent to 36
[ https://issues.apache.org/jira/browse/MSKINS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530467#comment-17530467 ] Hudson commented on MSKINS-178: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-fluido-skin » master #10 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-fluido-skin/job/master/10/ > Upgrade Parent to 36 > > > Key: MSKINS-178 > URL: https://issues.apache.org/jira/browse/MSKINS-178 > Project: Maven Skins > Issue Type: Dependency upgrade > Components: Fluido Skin >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: fluido-1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MRESOLVER-255) Update Jetty to 9.4.46 (test dependency)
[ https://issues.apache.org/jira/browse/MRESOLVER-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530389#comment-17530389 ] Hudson commented on MRESOLVER-255: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #27 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/27/ > Update Jetty to 9.4.46 (test dependency) > > > Key: MRESOLVER-255 > URL: https://issues.apache.org/jira/browse/MRESOLVER-255 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 1.8.1 > > > Update Jetty used in maven-resolver-transport-http tests to latest 9.x > version. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MPMD-329) Upgrade to PMD 6.45.0
[ https://issues.apache.org/jira/browse/MPMD-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530368#comment-17530368 ] Hudson commented on MPMD-329: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pmd-plugin » master #21 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/21/ > Upgrade to PMD 6.45.0 > - > > Key: MPMD-329 > URL: https://issues.apache.org/jira/browse/MPMD-329 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7464) Warn about using read-only parameters for Mojo in configuration
[ https://issues.apache.org/jira/browse/MNG-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530367#comment-17530367 ] Hudson commented on MNG-7464: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-731 #4 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-731/4/ > Warn about using read-only parameters for Mojo in configuration > --- > > Key: MNG-7464 > URL: https://issues.apache.org/jira/browse/MNG-7464 > Project: Maven > Issue Type: New Feature >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7464) Warn about using read-only parameters for Mojo in configuration
[ https://issues.apache.org/jira/browse/MNG-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530361#comment-17530361 ] Hudson commented on MNG-7464: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-731 #3 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-731/3/ > Warn about using read-only parameters for Mojo in configuration > --- > > Key: MNG-7464 > URL: https://issues.apache.org/jira/browse/MNG-7464 > Project: Maven > Issue Type: New Feature >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MINSTALL-174) Upgrade maven-plugin parent to 36
[ https://issues.apache.org/jira/browse/MINSTALL-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530350#comment-17530350 ] Hudson commented on MINSTALL-174: - Build succeeded in Jenkins: Maven » Maven TLP » maven-install-plugin » master #7 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-install-plugin/job/master/7/ > Upgrade maven-plugin parent to 36 > - > > Key: MINSTALL-174 > URL: https://issues.apache.org/jira/browse/MINSTALL-174 > Project: Maven Install Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.0.0-M2 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7404) Change from deprecated WARNING to FAIL the build for usage of {X} placeholders rather than ${project.X}
[
https://issues.apache.org/jira/browse/MNG-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529391#comment-17529391
]
Hudson commented on MNG-7404:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #18
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/18/
> Change from deprecated WARNING to FAIL the build for usage of {X}
> placeholders rather than ${project.X}
> ---
>
> Key: MNG-7404
> URL: https://issues.apache.org/jira/browse/MNG-7404
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 4.0.0-alpha-1
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0-alpha-1
>
>
> Currently we produce a {{WARNING}} in case of using {{version}} or alike.
> I would suggest to change {{WARNING}} into a failing build in such use cases.
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for 'com.soebes.examples.j2ee:appasm:pom:1.0-SNAPSHOT'
> [WARNING] The expression ${version} is deprecated. Please use
> ${project.version} instead.
> {code}
> WDYT?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7404) Change from deprecated WARNING to FAIL the build for usage of {X} placeholders rather than ${project.X}
[
https://issues.apache.org/jira/browse/MNG-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529377#comment-17529377
]
Hudson commented on MNG-7404:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #25
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/25/
> Change from deprecated WARNING to FAIL the build for usage of {X}
> placeholders rather than ${project.X}
> ---
>
> Key: MNG-7404
> URL: https://issues.apache.org/jira/browse/MNG-7404
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 4.0.0-alpha-1
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0-alpha-1
>
>
> Currently we produce a {{WARNING}} in case of using {{version}} or alike.
> I would suggest to change {{WARNING}} into a failing build in such use cases.
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for 'com.soebes.examples.j2ee:appasm:pom:1.0-SNAPSHOT'
> [WARNING] The expression ${version} is deprecated. Please use
> ${project.version} instead.
> {code}
> WDYT?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MINDEXER-149) Deprecate Maven1 support
[ https://issues.apache.org/jira/browse/MINDEXER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529242#comment-17529242 ] Hudson commented on MINDEXER-149: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #29 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/29/ > Deprecate Maven1 support > > > Key: MINDEXER-149 > URL: https://issues.apache.org/jira/browse/MINDEXER-149 > Project: Maven Indexer > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 6.2.0 > > > The support is already under maintained and incomplete. Mark these as > deprecated, and drop as soon as possible. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MWAR-452) One page about Skinny WARs
[
https://issues.apache.org/jira/browse/MWAR-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529203#comment-17529203
]
Hudson commented on MWAR-452:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-war-plugin » master #9
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-war-plugin/job/master/9/
> One page about Skinny WARs
> --
>
> Key: MWAR-452
> URL: https://issues.apache.org/jira/browse/MWAR-452
> Project: Maven WAR Plugin
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.4.0
>
>
> We have:
> - https://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
> - https://maven.apache.org/plugins/maven-ear-plugin/examples/skinny-wars.html
> Both site contains the same information and very similar (almost identical)
> content.
> {{Skinny WARs}} is feature of {{m-ear-p}} so page should be maintained in one
> place in {{m-ear-p}} project.
> In {{m-war-p}} we can link to site in {{m-ear-p}} project.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MSITE-897) Upgrade Plexus Archiver to 4.2.7
[ https://issues.apache.org/jira/browse/MSITE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529098#comment-17529098 ] Hudson commented on MSITE-897: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #24 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/24/ > Upgrade Plexus Archiver to 4.2.7 > > > Key: MSITE-897 > URL: https://issues.apache.org/jira/browse/MSITE-897 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M1 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSITE-898) Upgrade Parent to 36
[ https://issues.apache.org/jira/browse/MSITE-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529099#comment-17529099 ] Hudson commented on MSITE-898: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #24 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/24/ > Upgrade Parent to 36 > > > Key: MSITE-898 > URL: https://issues.apache.org/jira/browse/MSITE-898 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M1 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSITE-892) Upgrade to Doxia/Doxia Sitetools to 2.0.0-M2
[ https://issues.apache.org/jira/browse/MSITE-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529076#comment-17529076 ] Hudson commented on MSITE-892: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #23 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/23/ > Upgrade to Doxia/Doxia Sitetools to 2.0.0-M2 > > > Key: MSITE-892 > URL: https://issues.apache.org/jira/browse/MSITE-892 > Project: Maven Site Plugin > Issue Type: Dependency upgrade > Components: doxia integration >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M1 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSITE-894) Upgrade Maven Reporting Exec to 2.0.0-M1
[ https://issues.apache.org/jira/browse/MSITE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529079#comment-17529079 ] Hudson commented on MSITE-894: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #23 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/23/ > Upgrade Maven Reporting Exec to 2.0.0-M1 > > > Key: MSITE-894 > URL: https://issues.apache.org/jira/browse/MSITE-894 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M1 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSITE-895) Upgrade plugins and components in ITs
[ https://issues.apache.org/jira/browse/MSITE-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529080#comment-17529080 ] Hudson commented on MSITE-895: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #23 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/23/ > Upgrade plugins and components in ITs > - > > Key: MSITE-895 > URL: https://issues.apache.org/jira/browse/MSITE-895 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M1 > > > * Maven Project Info Reports Plugin to 3.4.0 > * Taglist Maven Plugin to 3.0.0 > * Maven to 3.2.5 > * Maven Reporting Impl to 4.0.0-M1 > * Maven Plugin Plugin to 3.6.4 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MSITE-893) Upgrade Maven Reporting API to 4.0.0-M1
[ https://issues.apache.org/jira/browse/MSITE-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529078#comment-17529078 ] Hudson commented on MSITE-893: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #23 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/23/ > Upgrade Maven Reporting API to 4.0.0-M1 > --- > > Key: MSITE-893 > URL: https://issues.apache.org/jira/browse/MSITE-893 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M1 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7404) Change from deprecated WARNING to FAIL the build for usage of {X} placeholders rather than ${project.X}
[
https://issues.apache.org/jira/browse/MNG-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529019#comment-17529019
]
Hudson commented on MNG-7404:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #39
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/39/
> Change from deprecated WARNING to FAIL the build for usage of {X}
> placeholders rather than ${project.X}
> ---
>
> Key: MNG-7404
> URL: https://issues.apache.org/jira/browse/MNG-7404
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 4.0.0-alpha-1
>Reporter: Maarten Mulders
>Assignee: Maarten Mulders
>Priority: Minor
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0-alpha-1
>
>
> Currently we produce a {{WARNING}} in case of using {{version}} or alike.
> I would suggest to change {{WARNING}} into a failing build in such use cases.
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for 'com.soebes.examples.j2ee:appasm:pom:1.0-SNAPSHOT'
> [WARNING] The expression ${version} is deprecated. Please use
> ${project.version} instead.
> {code}
> WDYT?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MRESOURCES-282) Upgrade maven-plugin parent to 36
[ https://issues.apache.org/jira/browse/MRESOURCES-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529017#comment-17529017 ] Hudson commented on MRESOURCES-282: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-resources-plugin » master #11 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resources-plugin/job/master/11/ > Upgrade maven-plugin parent to 36 > - > > Key: MRESOURCES-282 > URL: https://issues.apache.org/jira/browse/MRESOURCES-282 > Project: Maven Resources Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MRESOURCES-277) Update plugin (requires Maven 3.2.5+)
[ https://issues.apache.org/jira/browse/MRESOURCES-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529014#comment-17529014 ] Hudson commented on MRESOURCES-277: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-resources-plugin » master #10 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resources-plugin/job/master/10/ > Update plugin (requires Maven 3.2.5+) > - > > Key: MRESOURCES-277 > URL: https://issues.apache.org/jira/browse/MRESOURCES-277 > Project: Maven Resources Plugin > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.3.0 > > > Update plugin: > * requires Maven 3.2.5+ > * maven bits set to provided scope > * update dependencies -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MRESOURCES-283) Require Java 8
[ https://issues.apache.org/jira/browse/MRESOURCES-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528967#comment-17528967 ] Hudson commented on MRESOURCES-283: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-resources-plugin » master #9 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resources-plugin/job/master/9/ > Require Java 8 > -- > > Key: MRESOURCES-283 > URL: https://issues.apache.org/jira/browse/MRESOURCES-283 > Project: Maven Resources Plugin > Issue Type: Task >Reporter: Sylwester Lachiewicz >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7466) Align Assembly Descriptor NS versions
[
https://issues.apache.org/jira/browse/MNG-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528820#comment-17528820
]
Hudson commented on MNG-7466:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #38
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/38/
> Align Assembly Descriptor NS versions
> -
>
> Key: MNG-7466
> URL: https://issues.apache.org/jira/browse/MNG-7466
> Project: Maven
> Issue Type: Task
> Components: Bootstrap Build
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Trivial
> Fix For: 3.8.6, 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> Minor, but descriptor name spaces used in XML are outdated, version 2.1.0 is
> used since eons, while the build still uses 2.0.0 namespace.
> In Maven build, the {{apache-maven}} module assembles the distribution
> (binary) package, there are the XML descriptors stored for
> maven-assembly-plugin.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7466) Align Assembly Descriptor NS versions
[
https://issues.apache.org/jira/browse/MNG-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528817#comment-17528817
]
Hudson commented on MNG-7466:
-
Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #24
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/24/
> Align Assembly Descriptor NS versions
> -
>
> Key: MNG-7466
> URL: https://issues.apache.org/jira/browse/MNG-7466
> Project: Maven
> Issue Type: Task
> Components: Bootstrap Build
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Trivial
> Fix For: 3.8.6, 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> Minor, but descriptor name spaces used in XML are outdated, version 2.1.0 is
> used since eons, while the build still uses 2.0.0 namespace.
> In Maven build, the {{apache-maven}} module assembles the distribution
> (binary) package, there are the XML descriptors stored for
> maven-assembly-plugin.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7466) Align Assembly Descriptor NS versions
[
https://issues.apache.org/jira/browse/MNG-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528812#comment-17528812
]
Hudson commented on MNG-7466:
-
Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #17
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/17/
> Align Assembly Descriptor NS versions
> -
>
> Key: MNG-7466
> URL: https://issues.apache.org/jira/browse/MNG-7466
> Project: Maven
> Issue Type: Task
> Components: Bootstrap Build
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Trivial
> Fix For: 3.8.6, 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> Minor, but descriptor name spaces used in XML are outdated, version 2.1.0 is
> used since eons, while the build still uses 2.0.0 namespace.
> In Maven build, the {{apache-maven}} module assembles the distribution
> (binary) package, there are the XML descriptors stored for
> maven-assembly-plugin.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7457) Warn about deprecated plugin Mojo
[ https://issues.apache.org/jira/browse/MNG-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528814#comment-17528814 ] Hudson commented on MNG-7457: - Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #17 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/17/ > Warn about deprecated plugin Mojo > - > > Key: MNG-7457 > URL: https://issues.apache.org/jira/browse/MNG-7457 > Project: Maven > Issue Type: New Feature >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > Plugin Mojo can be marked as deprecated by author. > Maven should log warnings if deprecated Mojo is used in build plan. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-5222) Maven 3 no longer logs warnings about deprecated plugin parameters.
[ https://issues.apache.org/jira/browse/MNG-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528813#comment-17528813 ] Hudson commented on MNG-5222: - Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #17 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/17/ > Maven 3 no longer logs warnings about deprecated plugin parameters. > --- > > Key: MNG-5222 > URL: https://issues.apache.org/jira/browse/MNG-5222 > Project: Maven > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0.3 >Reporter: Christian Schulte >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Providing a value for a deprecated plugin parameter, Maven 2.2.1 used to log > a warning. Currently Maven 3 does not. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MRELEASE-1085) Upgrade Maven Invoker to 3.2.0
[
https://issues.apache.org/jira/browse/MRELEASE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528550#comment-17528550
]
Hudson commented on MRELEASE-1085:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-release » master #22
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/22/
> Upgrade Maven Invoker to 3.2.0
> --
>
> Key: MRELEASE-1085
> URL: https://issues.apache.org/jira/browse/MRELEASE-1085
> Project: Maven Release Plugin
> Issue Type: Dependency upgrade
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
>
> Very old version {{2.2}} is used in project.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MRELEASE-1086) Upgrade Parent to 36
[ https://issues.apache.org/jira/browse/MRELEASE-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528437#comment-17528437 ] Hudson commented on MRELEASE-1086: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-release » master #21 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/21/ > Upgrade Parent to 36 > > > Key: MRELEASE-1086 > URL: https://issues.apache.org/jira/browse/MRELEASE-1086 > Project: Maven Release Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.0.0-M6 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MRELEASE-1022) release:prepare does not honor project.dev version predefined in release.properties
[
https://issues.apache.org/jira/browse/MRELEASE-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528333#comment-17528333
]
Hudson commented on MRELEASE-1022:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-release » master #19
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/19/
> release:prepare does not honor project.dev version predefined in
> release.properties
> ---
>
> Key: MRELEASE-1022
> URL: https://issues.apache.org/jira/browse/MRELEASE-1022
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.5.3
> Environment:
> C:\Users\fandre\Documents\MXW\RD\RD>C:\ASF\apache-maven-3.6.1\bin\mvn
> --version
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T21:00:29+02:00)
> Maven home: C:\ASF\apache-maven-3.6.1\bin\..
> Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: C:\Program
> Files\Java\jdk1.8.0_181\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: zosrothko
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.0.0-M6
>
> Attachments: mvn.log, pom.xml, pom.xml, pom.xml, release.properties,
> release.properties.dryRun
>
>
> Hi
> Using the release.properties defined as below
> {code:java}
> scm.tag=rd-2019.3
> project.rel.com.scort\:rd=2019.3
> project.dev.com.scort\:rd=2019.4-SNAPSHOT
> project.rel.com.scort.merge\:mergejar=1.2.0
> project.dev.com.scort.merge\:mergejar=1.2.0
> project.rel.com.scort.plugins\:mergejar=1.2.0
> project.dev.com.scort.plugins\:mergejar=1.2.0
> {code}
> with the command
> {code:java}
> mvn -B release:prepare -DdryRun=true
> {code}
> the maven-release-plugin does not use the specified 'project.dev' version to
> update the pom in the second phase. Here the log
> {code:java}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] RD
> [pom]
> [INFO] Jar Merger
> [jar]
> [INFO] MAVEN plugin to merge jar
> [maven-plugin]
> [INFO]
> [INFO] < com.scort:rd
> >
> [INFO] Building RD 2019.3-SNAPSHOT
> [1/3]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ rd ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **\pom.xml.next, **\release.properties,
> **\pom.xml.branch, **\pom.xml.tag, **\pom.xml.backup, **\pom.xml.releaseBackup
> [INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
> [INFO] Working directory: C:\Users\fandre\Documents\MXW\RD\RD
> [INFO] Executing: cmd.exe /X /C "git status --porcelain ."
> [INFO] Working directory: C:\Users\fandre\Documents\MXW\RD\RD
> [WARNING] Ignoring unrecognized line: ?? RD/release.properties.copy
> [INFO] Checking dependencies and plugins for snapshots ...
> [INFO] Transforming 'RD'...
> [INFO] Updating ${antmergejar} to 1.2.0
> [INFO] Updating ${mavenmergejar} to 1.2.0
> [INFO] Transforming 'Jar Merger'...
> [INFO] Transforming 'MAVEN plugin to merge jar'...
> [INFO] Not generating release POMs
> [INFO] Executing preparation goals - since this is simulation mode it is
> running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO]
>
> [INFO] [INFO] Reactor Build Order:
> [INFO] [INFO]
> [INFO] [INFO] RD
> [pom]
> [INFO] [INFO] Jar Merger
> [jar]
> [INFO] [INFO] MAVEN plugin to merge jar
> [maven-plugin]
> [INFO] [INFO]
> [INFO] [INFO] < com.scort:rd
> >
> [INFO] [INFO] Building RD 2019.3-SNAPSHOT
> [1/3]
> [INFO] [INFO] [ pom
> ]-
> [INFO] [INFO]
> [INFO] [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ rd ---
> [INFO] [INFO]
> [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven) @ rd ---
> [INFO] [INFO]
> [INFO] [INFO] --< com.scort.merge:mergejar
> >--
> [INFO] [INFO] Building
[jira] [Commented] (MWAR-454) Upgrade Parent to 36
[ https://issues.apache.org/jira/browse/MWAR-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527702#comment-17527702 ] Hudson commented on MWAR-454: - Build succeeded in Jenkins: Maven » Maven TLP » maven-war-plugin » master #8 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-war-plugin/job/master/8/ > Upgrade Parent to 36 > > > Key: MWAR-454 > URL: https://issues.apache.org/jira/browse/MWAR-454 > Project: Maven WAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MINDEXER-147) Move rootGroups and allGroups fields out of index
[ https://issues.apache.org/jira/browse/MINDEXER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527586#comment-17527586 ] Hudson commented on MINDEXER-147: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #28 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/28/ > Move rootGroups and allGroups fields out of index > - > > Key: MINDEXER-147 > URL: https://issues.apache.org/jira/browse/MINDEXER-147 > Project: Maven Indexer > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 6.2.0 > > > These two were (mis) using index and were stored just to provide users like > IDEs the information that was anyway rebuilt on every update. > Make these two in memory, but keep it in written format to keep backward > compatibility. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MWAR-450) ISO8859-1 properties files get changed into UTF-8 when filtered
[
https://issues.apache.org/jira/browse/MWAR-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527502#comment-17527502
]
Hudson commented on MWAR-450:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-war-plugin » master #7
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-war-plugin/job/master/7/
> ISO8859-1 properties files get changed into UTF-8 when filtered
> ---
>
> Key: MWAR-450
> URL: https://issues.apache.org/jira/browse/MWAR-450
> Project: Maven WAR Plugin
> Issue Type: Improvement
> Components: filtering
>Affects Versions: 3.3.2
>Reporter: Dennis Lundberg
>Priority: Major
> Fix For: 3.4.0
>
>
> This issue is similar to
> https://issues.apache.org/jira/browse/MRESOURCES-171, but for filtering web
> resources in maven-war-plugin.
> We add properties files that have ISO-8859-1 encoding, as per the Java 8
> requirements, as web resources in a war project. When these resources are
> filtered they get converted to the encoding specified by the
> project.build.sourceEncoding. There is a parameter resourceEncoding that can
> be used to change the encoding for web reources, but it applies to all web
> resource files which is not always what you want.
> Here is the configuration used:
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-war-plugin
> 3.3.2
>
>
>
> WEB-INF/classes
> true
> src/main/webapp/WEB-INF/classes
>
>
>
>
>
>
> {code}
> We propose to add a new parameter propertiesEncoding to the AbstractWarMojo.
> If the value of this parameter is set and filtering is enabled and a web
> resource file is a properties file, then the value of the parameter is used
> as encoding when filtering the file.
> If the parameter is not specified it defaults to
> project.build.sourceEncoding, thus keeping the current behavior of the plugin
> unchanged.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MINDEXER-146) Fix issues reported by Lucene 9
[ https://issues.apache.org/jira/browse/MINDEXER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527471#comment-17527471 ] Hudson commented on MINDEXER-146: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #27 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/27/ > Fix issues reported by Lucene 9 > --- > > Key: MINDEXER-146 > URL: https://issues.apache.org/jira/browse/MINDEXER-146 > Project: Maven Indexer > Issue Type: Bug >Affects Versions: 6.1.1 >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 6.2.0 > > > When attempted Lucene 9.1.0 upgrade, there were several issues that failed > tests: > * uses of deprecated RAMDirectory > * omitNorms and indexOptions flops happening for same fields > Apply all the fixes so upgrade to Lucene 9.1.0 becomes no brainer, but it > will not happen now, as it requires Java11 level. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MRESOLVER-252) Make LRM path composition reusable
[ https://issues.apache.org/jira/browse/MRESOLVER-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527467#comment-17527467 ] Hudson commented on MRESOLVER-252: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #26 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/26/ > Make LRM path composition reusable > -- > > Key: MRESOLVER-252 > URL: https://issues.apache.org/jira/browse/MRESOLVER-252 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 1.8.1 > > > LocalRepositoryManager path composition was enclosed > into SimpleLocalRepositoryManager in not-quite reusable > manner. Make it reusable, by making it into a component. > Currently FileProvidedChecksumsSource was reusing local > paths, is adjusted now. > Also, make LRM implementations more encapsulated and > clear up many ctors leaving only one for simplicity. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MRESOLVER-253) Dynamic prefixes for LRM
[ https://issues.apache.org/jira/browse/MRESOLVER-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527468#comment-17527468 ] Hudson commented on MRESOLVER-253: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #26 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/26/ > Dynamic prefixes for LRM > > > Key: MRESOLVER-253 > URL: https://issues.apache.org/jira/browse/MRESOLVER-253 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 1.8.1 > > > Enhances existing "enhanced" LRM (local repository manager) with "prefix" > from from path prefix composer. Default behavior is not changed (will not use > prefix, local repository will work as before). > The point in change is that it introduce a "composer", that is composing LRM > path prefixes, and is able to apply different strategies, and split local > repository into "installed" (locally built and installed) and "cached" > (downloaded from remote), etc. > There are several composer options out of the box: > * split between "cached" and locally "installed" artifacts > * split "cached" artifacts based on their origin (remote repository) > * split between "release" and "snapshot" versioned artifacts > These properties can all be configured via resolver "configuration", > essentially via session configuration. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7457) Warn about deprecated plugin Mojo
[ https://issues.apache.org/jira/browse/MNG-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527189#comment-17527189 ] Hudson commented on MNG-7457: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #37 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/37/ > Warn about deprecated plugin Mojo > - > > Key: MNG-7457 > URL: https://issues.apache.org/jira/browse/MNG-7457 > Project: Maven > Issue Type: New Feature >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > Plugin Mojo can be marked as deprecated by author. > Maven should log warnings if deprecated Mojo is used in build plan. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7457) Warn about deprecated plugin Mojo
[ https://issues.apache.org/jira/browse/MNG-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527186#comment-17527186 ] Hudson commented on MNG-7457: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #23 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/23/ > Warn about deprecated plugin Mojo > - > > Key: MNG-7457 > URL: https://issues.apache.org/jira/browse/MNG-7457 > Project: Maven > Issue Type: New Feature >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > Plugin Mojo can be marked as deprecated by author. > Maven should log warnings if deprecated Mojo is used in build plan. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7457) Warn about deprecated plugin Mojo
[ https://issues.apache.org/jira/browse/MNG-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527152#comment-17527152 ] Hudson commented on MNG-7457: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #22 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/22/ > Warn about deprecated plugin Mojo > - > > Key: MNG-7457 > URL: https://issues.apache.org/jira/browse/MNG-7457 > Project: Maven > Issue Type: New Feature >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > Plugin Mojo can be marked as deprecated by author. > Maven should log warnings if deprecated Mojo is used in build plan. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7457) Warn about deprecated plugin Mojo
[ https://issues.apache.org/jira/browse/MNG-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527127#comment-17527127 ] Hudson commented on MNG-7457: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #36 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/36/ > Warn about deprecated plugin Mojo > - > > Key: MNG-7457 > URL: https://issues.apache.org/jira/browse/MNG-7457 > Project: Maven > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 4.0.0-alpha-1, 4.0.0 > > > Plugin Mojo can be marked as deprecated by author. > Maven should log warnings if deprecated Mojo is used in build plan. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-5222) Maven 3 no longer logs warnings about deprecated plugin parameters.
[ https://issues.apache.org/jira/browse/MNG-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527128#comment-17527128 ] Hudson commented on MNG-5222: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #36 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/36/ > Maven 3 no longer logs warnings about deprecated plugin parameters. > --- > > Key: MNG-5222 > URL: https://issues.apache.org/jira/browse/MNG-5222 > Project: Maven > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0.3 >Reporter: Christian Schulte >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Providing a value for a deprecated plugin parameter, Maven 2.2.1 used to log > a warning. Currently Maven 3 does not. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7400) Allow more WorkspaceReaders to participate
[
https://issues.apache.org/jira/browse/MNG-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527096#comment-17527096
]
Hudson commented on MNG-7400:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Allow more WorkspaceReaders to participate
> --
>
> Key: MNG-7400
> URL: https://issues.apache.org/jira/browse/MNG-7400
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.8.4
>Reporter: Christoph Läubrich
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> Currently there are two kind of {{WorkspaceReaders}} the reactor one and the
> one obtained from the {{RepositorySystemSession}} (which is eed by an IDE
> scoped component in
> {{org.apache.maven.internal.aether.DefaultRepositorySystemSessionFactory}}).
> In [Tycho|https://github.com/eclipse/tycho] we have the demand to supply a
> {{WorkspaceReader}} as there is a so called "target platform" as the source
> of artifacts.
> Now it does not seem correct to declare it as an IDE, and of course we don't
> want to block the IDE use-case.
> Another issue is that at the time the IDE component is injected there is no
> session and thus a session scoped component won't work as well so even if we
> would use this we are rather "blind".
> It would be good to have maven discover {{WorkspaceReaders}} as it discovers
> {{AbstractMavenLifecycleParticipants}} in the following way, right before the
> session is fixed:
> {code:java}
> for ( WorkspaceReader reader : getWorkspaceReader( session.getProjects() ) )
> {
> //chain them together with the current workspace reader(s)
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7391) add MojoExecution strategy and runner required by Maven Build Cache Extension
[ https://issues.apache.org/jira/browse/MNG-7391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527111#comment-17527111 ] Hudson commented on MNG-7391: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > add MojoExecution strategy and runner required by Maven Build Cache Extension > - > > Key: MNG-7391 > URL: https://issues.apache.org/jira/browse/MNG-7391 > Project: Maven > Issue Type: New Feature > Components: Core >Reporter: Herve Boutemy >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1 > > > Maven Build Cache Extension has been provided as a maven-core update, but > extracted to a separate module then a separate Git repository to provide an > extension: see MNG-7129 == MBUILDCACHE-1 > the extension just requires a small API in Maven core to be able to inject > Build Cache: MojoExecution strategy and runner > By default, MojoExecution strategy is to run Mojos > Build Cache Extension can has a more advanced strategy that can introduce > cache = inject MojoExecution result taken from cache to avoid running the Mojo -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7438) add execution id to "Configuring mojo xxx with basic configurator" debug message
[
https://issues.apache.org/jira/browse/MNG-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527121#comment-17527121
]
Hudson commented on MNG-7438:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> add execution id to "Configuring mojo xxx with basic configurator" debug
> message
>
>
> Key: MNG-7438
> URL: https://issues.apache.org/jira/browse/MNG-7438
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Affects Versions: 3.8.5
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> currently, when running goals/mojos, we have in debug logs
> {noformat}
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> org.example.apache.maven.execution ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator -->
> [DEBUG] (s) additionalClasspathElements = []
> [DEBUG] (s) basedir = /home/herve/tmp/org.example.apache.maven.execution
> {noformat}
> on the "{{Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator}}" line, it completely hides the fact that configuration is
> valid for an execution id, that has a default value when nobody defined any
> (see https://maven.apache.org/guides/mini/guide-default-execution-ids.html )
> Just adding "{{execution 'default-test'}}" would make things more clear so
> people learn about execution ids
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
> 'default-test' with basic configurator -->
> {noformat}
> h2. final debug messages
> {noformat}
> [DEBUG] Loading mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo execution
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test:default-test'
> with basic configurator -->
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7457) Warn about deprecated plugin Mojo
[ https://issues.apache.org/jira/browse/MNG-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527124#comment-17527124 ] Hudson commented on MNG-7457: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Warn about deprecated plugin Mojo > - > > Key: MNG-7457 > URL: https://issues.apache.org/jira/browse/MNG-7457 > Project: Maven > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 4.0.0-alpha-1, 4.0.0 > > > Plugin Mojo can be marked as deprecated by author. > Maven should log warnings if deprecated Mojo is used in build plan. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7055) Using MINSTALL/DEPLOY 3.0.0-M1+ does not write plugin information into maven-metadata.xml
[
https://issues.apache.org/jira/browse/MNG-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527123#comment-17527123
]
Hudson commented on MNG-7055:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Using MINSTALL/DEPLOY 3.0.0-M1+ does not write plugin information into
> maven-metadata.xml
> -
>
> Key: MNG-7055
> URL: https://issues.apache.org/jira/browse/MNG-7055
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Plugins and Lifecycle
>Reporter: Elliotte Rusty Harold
>Assignee: Tamás Cservenák
>Priority: Blocker
> Fix For: 3.9.0, 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> Copying [~michael-o]'s comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7370) Upgrade Maven Wagon to 3.5.1
[ https://issues.apache.org/jira/browse/MNG-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527080#comment-17527080 ] Hudson commented on MNG-7370: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Upgrade Maven Wagon to 3.5.1 > > > Key: MNG-7370 > URL: https://issues.apache.org/jira/browse/MNG-7370 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-5222) Maven 3 no longer logs warnings about deprecated plugin parameters.
[ https://issues.apache.org/jira/browse/MNG-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527119#comment-17527119 ] Hudson commented on MNG-5222: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Maven 3 no longer logs warnings about deprecated plugin parameters. > --- > > Key: MNG-5222 > URL: https://issues.apache.org/jira/browse/MNG-5222 > Project: Maven > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0.3 >Reporter: Christian Schulte >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Providing a value for a deprecated plugin parameter, Maven 2.2.1 used to log > a warning. Currently Maven 3 does not. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7377) Add .vscode/ to .gitignore
[ https://issues.apache.org/jira/browse/MNG-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527081#comment-17527081 ] Hudson commented on MNG-7377: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Add .vscode/ to .gitignore > -- > > Key: MNG-7377 > URL: https://issues.apache.org/jira/browse/MNG-7377 > Project: Maven > Issue Type: Task >Reporter: Jeff Hodges >Assignee: Michael Osipov >Priority: Major > > vscode adds a `.vscode` directory to the top of a git repo it's opened in. > This is harmless, but the apache-rat plugin configured in the maven's > top-level `pom.xml` sounds the alarm on it and doesn't even allow the code to > compile. That means anyone reading maven's code in vscode will have a failing > build > I've got a patch I'll post that ignores the `.vscode` dir in the rat's config > and in `.gitignore`. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7453) Upgrade Maven Resolver to 1.8.0
[ https://issues.apache.org/jira/browse/MNG-7453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527122#comment-17527122 ] Hudson commented on MNG-7453: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Upgrade Maven Resolver to 1.8.0 > --- > > Key: MNG-7453 > URL: https://issues.apache.org/jira/browse/MNG-7453 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > Maven Resolver 1.8 will bring multiple improvements in many area: extensible > checksum algorithms, provided checksum, ability for signature resolution, > smart checksum, new BF collection along with "old" DF collector, etc. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7432) [REGRESSION] Resolver session contains non-MavenWorkspaceReader
[ https://issues.apache.org/jira/browse/MNG-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527118#comment-17527118 ] Hudson commented on MNG-7432: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > [REGRESSION] Resolver session contains non-MavenWorkspaceReader > --- > > Key: MNG-7432 > URL: https://issues.apache.org/jira/browse/MNG-7432 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.5 >Reporter: Falko Modler >Assignee: Tamás Cservenák >Priority: Critical > Fix For: 3.8.6, 3.9.0, 4.0.0 > > > As Resolver session contains non-MavenWorkspaceReader, the reactor models > (already resolved w/ profiles applied) are re-built when using Resolver > within Mojo, instead to get them via ReactorReader as expected. The rebuilt > models will lack explicit (-P on CLI) profiles applied, as resolver itself is > not maven aware, hence there is no way to "tell" resolver to apply them. > Building reactor models w/ profiles applied is NOT done using resolver, but > by Maven when loading up reactor, as profiles are NOT applied for downstream > transitive dependencies (see discussion on MNG-1388 why). > --- > The README of the following reproducer says it all: > https://github.com/aloubyansky/playground/tree/maven-3.8.5-profile-activation > Initially discussed here: > https://github.com/quarkusio/quarkus/pull/24285#issuecomment-1067368625 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7454) Include resolver-transport-http in Maven
[
https://issues.apache.org/jira/browse/MNG-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527120#comment-17527120
]
Hudson commented on MNG-7454:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Include resolver-transport-http in Maven
>
>
> Key: MNG-7454
> URL: https://issues.apache.org/jira/browse/MNG-7454
> Project: Maven
> Issue Type: New Feature
> Components: Dependencies
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> We should include maven-resolver-transport-http (along with existing
> maven-resolver-transport-wagon) but retain Wagon as default transport, while
> offer ability for users to use http transport to utilize new resolver
> features like "smart checksums".
> On positive side, this will finally get rid of shaded httpClient and
> wagon-http-shaded as well.
> To switch transport use {{-Dmaven.resolver.transport}} with following values:
> * {{wagon}} - to use wagon (is default as well)
> * {{native}} - to use resolver own highly optimized HTTP and FILE transport
> (supports "smart checksums")
> * {{auto}} - to rely on resolver own discovery, or if another transport
> extension used
> The selected transport can be seen in debug (-X) output on line `[DEBUG]
> Using transporter XXX...`
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7441) Update Version of (optional) Logback to Address CVE-2021-42550
[
https://issues.apache.org/jira/browse/MNG-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527117#comment-17527117
]
Hudson commented on MNG-7441:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Update Version of (optional) Logback to Address CVE-2021-42550
> --
>
> Key: MNG-7441
> URL: https://issues.apache.org/jira/browse/MNG-7441
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.8.5
>Reporter: Mac Hale
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 3.8.6, 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> [CVE-2021-42550|https://nvd.nist.gov/vuln/detail/CVE-2021-42550] is present
> in Logback versions 1.2.7 and earlier. Maven (optionally) uses v 1.2.1.
> Please update to Logback 1.2.9, which includes a fix as per
> [https://jira.qos.ch/browse/LOGBACK-1591|[https://jira.qos.ch/browse/LOGBACK-1591].]
> I see ch.qos.logback 1.2.1 in {{./pom.xml}} and ch.qos.logback without a
> version specified in {{./maven-embedder/pom.xml}}
> But I'm no expert on this code base so it's possible there are other
> versioned references.
> Edit: One could argue, as the Logback team has done, that the CVE is
> unimportant since in order to exploit it one must already have compromised
> the system. However, security scanners pick this up as an issue, causing
> unnecessary work and justifications.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7452) Remove JDK7 run on Maven 3.9.X Branch
[ https://issues.apache.org/jira/browse/MNG-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527116#comment-17527116 ] Hudson commented on MNG-7452: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Remove JDK7 run on Maven 3.9.X Branch > - > > Key: MNG-7452 > URL: https://issues.apache.org/jira/browse/MNG-7452 > Project: Maven > Issue Type: Task >Affects Versions: 3.9.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.9.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7447) Several Improvements by using Stream API
[ https://issues.apache.org/jira/browse/MNG-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527115#comment-17527115 ] Hudson commented on MNG-7447: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Several Improvements by using Stream API > > > Key: MNG-7447 > URL: https://issues.apache.org/jira/browse/MNG-7447 > Project: Maven > Issue Type: Sub-task >Affects Versions: 3.9.0, 4.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.9.0, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7349) Limit relocation warning message to direct dependencies only
[
https://issues.apache.org/jira/browse/MNG-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527093#comment-17527093
]
Hudson commented on MNG-7349:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Limit relocation warning message to direct dependencies only
>
>
> Key: MNG-7349
> URL: https://issues.apache.org/jira/browse/MNG-7349
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Affects Versions: 3.8.3, 3.8.4
>Reporter: Joep Weijers
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> In the
> [commit|https://github.com/apache/maven/commit/a1ba33069fad1fb9c6e9cd458ad233ff3a74aadd]
> that solved MNG-7253, the check for relocations was moved from the
> DefaultProjectDependenciesResolver to the DefaultArtifactDescriptorReader.
> This means that the relocation messages are not only shown on project
> dependencies, but on any artifact that is read.
> This may lead to unfixable WARNINGS in the output if a plugin transitively
> uses a relocated artifact.
> This can be reproduced by calling {{mvn dependency:tree}} with a simple,
> empty {{{}pom.xml{}}}. This will give the following warning:
> {code:java}
> [WARNING] The artifact xml-apis:xml-apis:jar:2.0.2 has been relocated to
> xml-apis:xml-apis:jar:1.0.b2
> {code}
> The default maven-dependency-plugin version is 2.8 and it depends on
> {{{}org.apache.maven.reporting:maven-reporting-impl:2.0.5{}}}, which depends
> on {{commons-validator:commons-validator:1.2.0}} which depends on
> {{{}xml-apis:xml-apis:2.0.2{}}}.
> In this particular case, updating to a recent maven-dependency-plugin version
> solves the issue. But since the transitive dependencies of plugins are not
> under the control of the end users, I don't think this warning should be
> shown.
> *Workaround:*
> Stay on Maven 3.8.2 or disable logging on the DefaultArtifactDescriptorReader:
> {code:java}
> -Dorg.slf4j.simpleLogger.log.org.apache.maven.repository.internal.DefaultArtifactDescriptorReader=error
> {code}
> Although this disables all relocation messages, including the ones you might
> be interested in.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7252) Fix warnings issued by dependency:analyze
[
https://issues.apache.org/jira/browse/MNG-7252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527070#comment-17527070
]
Hudson commented on MNG-7252:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Fix warnings issued by dependency:analyze
> -
>
> Key: MNG-7252
> URL: https://issues.apache.org/jira/browse/MNG-7252
> Project: Maven
> Issue Type: Task
> Components: Dependencies
>Affects Versions: 3.8.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Labels: up-for-grabs
> Fix For: 3.8.3
>
>
> At least the following needs to be addressed:
> {noformat}
> 373 [INFO] --- maven-dependency-plugin:3.1.1:analyze (default-cli) @
> maven-model-builder ---
> 374 [WARNING] Used undeclared dependencies found:
> 375 [WARNING]org.apache.commons:commons-lang3:jar:3.8.1:compile
> 633 [INFO] --- maven-dependency-plugin:3.1.1:analyze (default-cli) @
> maven-resolver-provider ---
> 634 [WARNING] Unused declared dependencies found:
> 638 [WARNING]org.slf4j:slf4j-api:jar:1.7.32:compile
> 724 [INFO] --- maven-dependency-plugin:3.1.1:analyze (default-cli) @
> maven-core ---
> 725 [WARNING] Used undeclared dependencies found:
> 726 [WARNING]org.slf4j:slf4j-api:jar:1.7.32:compile
> 727 [WARNING]org.codehaus.plexus:plexus-interpolation:jar:1.26:compile
> 861 [INFO] --- maven-dependency-plugin:3.1.1:analyze (default-cli) @
> maven-embedder ---
> 864 [WARNING] Unused declared dependencies found:
> 865 [WARNING]javax.annotation:javax.annotation-api:jar:1.2:compile
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7236) The DefaultPluginVersionResolver should cache results for the session
[ https://issues.apache.org/jira/browse/MNG-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527068#comment-17527068 ] Hudson commented on MNG-7236: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > The DefaultPluginVersionResolver should cache results for the session > - > > Key: MNG-7236 > URL: https://issues.apache.org/jira/browse/MNG-7236 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.8.3, 4.0.0-alpha-1, 4.0.0 > > > During a reactor build, it would be better to cache the resolved version for > plugins, both for performance reasons and for reproducibility. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7408) Explain reporting plugin version automatic selection (in Maven 3)
[ https://issues.apache.org/jira/browse/MNG-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527095#comment-17527095 ] Hudson commented on MNG-7408: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Explain reporting plugin version automatic selection (in Maven 3) > - > > Key: MNG-7408 > URL: https://issues.apache.org/jira/browse/MNG-7408 > Project: Maven > Issue Type: Improvement > Components: Sites Reporting >Affects Versions: 3.8.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > > reporting plugin version looks like normal version = you need to define a > version for build stability > https://maven.apache.org/ref/3.8.4/maven-model/maven.html#class_reporting > in Maven 2, it did not even benefit from pluginManagement version selection > but since Maven 3 MNG-4162, it benefits not only from pluginManagement > version but also from plugin: we need to make that clear, because versions of > report plugins are a pain for users who don't know about this, because it > force them to define a property that will be used both in > pluginManagement/plugin and reporting > and since Maven Site Plugin 3.4, it also benefits from pluginManagement > configuration > see https://maven.apache.org/shared/maven-reporting-exec/ -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7386) ModelMerger$MergingList is not serializable
[
https://issues.apache.org/jira/browse/MNG-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527092#comment-17527092
]
Hudson commented on MNG-7386:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> ModelMerger$MergingList is not serializable
> ---
>
> Key: MNG-7386
> URL: https://issues.apache.org/jira/browse/MNG-7386
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.6.3, 3.8.4
>Reporter: Kostiantyn Liutovych
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> Hello!
> [Spotless Maven plugin|https://github.com/diffplug/spotless] serializes
> {{org.apache.maven.model.Plugin}} instances to fingerprint plugin's
> configuration. Serialization fails for Maven 3.6.3 with:
> {code}
> java.io.NotSerializableException:
> org.apache.maven.model.merge.ModelMerger$MergingList
> {code}
> when plugin configuration comes from {{pluginManagement}}. Class
> {{org.apache.maven.model.Plugin}} implements {{java.io.Serializable}},
> however nested class {{org.apache.maven.model.merge.ModelMerger$MergingList}}
> does not.
> Would it be possible to make {{MergingList}} serializable or make
> {{Plugin#dependencies}} field always hold a serializable collection?
> Related issue for the Spotless Maven plugin:
> https://github.com/diffplug/spotless/issues/1073 and PR with a workaround
> https://github.com/diffplug/spotless/pull/1074.
> Thank you!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-6972) Allow access to org.apache.maven.graph
[
https://issues.apache.org/jira/browse/MNG-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527110#comment-17527110
]
Hudson commented on MNG-6972:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Allow access to org.apache.maven.graph
> --
>
> Key: MNG-6972
> URL: https://issues.apache.org/jira/browse/MNG-6972
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading, Plugin API
>Affects Versions: 3.6.3
>Reporter: Michael Kroll
>Assignee: Michael Osipov
>Priority: Major
> Labels: easyfix, pull-request-available
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> Hi
> maven doesn't export org.apache.maven.graph package in
> maven-core/src/main/resources/META-INF/maven/extension.xml so the
> GraphBuilder is not usable in extensions.
> {code:java}
> // leads to java.lang.NoClassDefFoundError:
> Lorg/apache/maven/graph/GraphBuilder;
> @Requirement( hint = GraphBuilder.HINT )
> private GraphBuilder graphBuilder;
> {code}
> Background: if one build extension adds dependencies and another build
> extension uses {{session.getProjectDependencyGraph()}}, then the dependency
> graph is out of date. This is because the graph is only rebuilt after
> executing _all_ extensions. One solution to this would be to update the
> {{MavenSession}} and setting the new dependency graph in the first extension,
> but for this we need access to the {{GraphBuilder}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7445) to refactor some useless code
[ https://issues.apache.org/jira/browse/MNG-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527114#comment-17527114 ] Hudson commented on MNG-7445: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > to refactor some useless code > - > > Key: MNG-7445 > URL: https://issues.apache.org/jira/browse/MNG-7445 > Project: Maven > Issue Type: Improvement > Components: Core >Affects Versions: 3.8.5 > Environment: macos, linux ,windwos >Reporter: jackyHu >Assignee: Karl Heinz Marbaise >Priority: Trivial > Labels: refactor > Fix For: 3.8.6, 3.9.0, 4.0.0 > > Attachments: wenjian.jpg > > Original Estimate: 1h > Remaining Estimate: 1h > > the code at > maven-core/src/main/java/org/apache/maven/settings/DefaultMavenSettingsBuilder.java > and the return statement (at line 158 and 162)been writen twice ,but they > could be only write once. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7381) Shorten parallel builder thread name to artifactId, conditionally with groupId
[
https://issues.apache.org/jira/browse/MNG-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527090#comment-17527090
]
Hudson commented on MNG-7381:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Shorten parallel builder thread name to artifactId, conditionally with groupId
> --
>
> Key: MNG-7381
> URL: https://issues.apache.org/jira/browse/MNG-7381
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.8.2, 3.8.3, 3.8.4
>Reporter: Falko Modler
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> Following up on MNG-6471, the thread name that is now generated can easily
> exceed 60 chars or more, e.g.:
> {noformat}
> [mvn-builder-de.somecorp.foo.barbazx:register-server:jar:2.0.0.local-dev3] ...
> {noformat}
> This devaluates {{-Dorg.slf4j.simpleLogger.showThreadName=true}} as the only
> easily availble option to differentiate where a logline comes from.
> As discussed
> [here|https://github.com/apache/maven/pull/177#issuecomment-1005975037] (and
> in the following comments), one idea is to make the pattern configurable (or
> simpler, have a toggle to include the entire module id or only its
> artifactId).
> A slightly different approach could try to detect whether there are
> "duplicate" artifactIds in the reactor and only append the groupId for those.
> In any way, type, classfier and version don't seem to add anything valuable.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7350) Introduce a factory for ModelCache
[
https://issues.apache.org/jira/browse/MNG-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527112#comment-17527112
]
Hudson commented on MNG-7350:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Introduce a factory for ModelCache
> --
>
> Key: MNG-7350
> URL: https://issues.apache.org/jira/browse/MNG-7350
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.9.0, 4.0.x-candidate
>
>
> {{mvnd}} does redefine a few maven classes in order to plugin its caching
> layer.
> One of those class is the {{ProjectBuilder}}, but that's only because the
> {{ModelCache}} is created using a direct call on the implementation.
> This ticket aims to introduce a {{ModelCacheFactory}} so that {{mvnd}} can
> simply define a custom factory instead of redefining the full
> {{ProjectBuilder}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-6878) Upgrade Guice to 4.2.3
[
https://issues.apache.org/jira/browse/MNG-6878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527106#comment-17527106
]
Hudson commented on MNG-6878:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Upgrade Guice to 4.2.3
> --
>
> Key: MNG-6878
> URL: https://issues.apache.org/jira/browse/MNG-6878
> Project: Maven
> Issue Type: Dependency upgrade
>Reporter: Sylwester Lachiewicz
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> h4. Changes since Guice 4.2.2 [https://github.com/google/guice/wiki/Guice423]
> [http://google.github.io/guice/api-docs/4.2.3/api-diffs/changes.html]
> * Java14 support (updated asm).
> * Added {{Injector.getElements}} API, to expose all Element SPI types from
> the Injector.
> * Added {{Injector.getAllMembersInjectorInjectionPoints}} API, to expose
> injection points created by arbitrary members injection.
> * Added {{getAlternateKeys}} to Multibinder SPI types
> ({{MultibinderBinding}}, {{MapBinderBinding}}, {{OptionalBinderBinding}}), to
> explicitly list the other keys these bindings are available as.
> * Scan for (and bind) @Provides-like methods in a consistent ordering,
> rather than relying on the non-deterministic Class.getDeclaredMembers
> ordering.
> * Update {{DaggerAdapter}} to work with newer dagger code.
> * Fixed a [subtle
> bug|https://github.com/google/guice/commit/f8cc1718a33a868e9951f7d3d6b4f74d8b1a1548]
> with eager singleton evaluation.
> * Updated {{@RequestScope}}'s scope annotation to the JSR330 {{@Scope}}, so
> it can be reused by non-Guice DI systems.
> * Clarified the error message when an injectable constructor is missing.
> * Add deprecated overloads to various {{Modules}} methods, to make it
> clearer when calling them is unnecessary.
> * Added factory methods to {{Modules}} for common Binder configuration
> methods, to make it easier to configure them.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-6326) Build continues when core extensions aren't found
[ https://issues.apache.org/jira/browse/MNG-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527085#comment-17527085 ] Hudson commented on MNG-6326: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Build continues when core extensions aren't found > - > > Key: MNG-6326 > URL: https://issues.apache.org/jira/browse/MNG-6326 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.5.2 >Reporter: Matt Biggs >Assignee: Guillaume Nodet >Priority: Critical > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > > If you define a core extension in *.mvn/extensions.xml* which then can't be > retrieved/found the build issues a warning and then continues leading to > unexpected behaviour depending on the functionality provided by the > extension. > If the extension is defined in the pom and not found the build fails. I would > have expected it to fail when not found in the external extensions.xml file > too as it's quite easy to miss the fact it failed to retrieve it. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7395) Support interpolation in extensions.xml
[
https://issues.apache.org/jira/browse/MNG-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527098#comment-17527098
]
Hudson commented on MNG-7395:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Support interpolation in extensions.xml
> ---
>
> Key: MNG-7395
> URL: https://issues.apache.org/jira/browse/MNG-7395
> Project: Maven
> Issue Type: New Feature
>Reporter: Christoph Läubrich
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> Currently an entry has to be the following form:
> {code:xml}
>
> org.eclipse.tycho
> tycho-build
> 2.7.0-SNAPSHOT
>
> {code}
> This has the drawback that I always need to edit the extension.xml file and
> there is no way to specify it on the commandline.
> The proposal is to allow the follwoing:
> {code:xml}
>
> org.eclipse.tycho
> tycho-build
> ${tycho-version|2.6.0}
>
> {code}
> I would then expect the following:
> # If no systemproperty with name 'tycho-version' exits, the value after the |
> is used as a default
> # If a systemproperty with name 'tycho-version' exits it is used as a version
> That way I can call mvn -Dtycho-version=2.7.0-SNAPSHOT clean install to
> override the default version.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-6826) Remove condition check for JDK8+ in FileSizeFormatTest
[ https://issues.apache.org/jira/browse/MNG-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527108#comment-17527108 ] Hudson commented on MNG-6826: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Remove condition check for JDK8+ in FileSizeFormatTest > -- > > Key: MNG-6826 > URL: https://issues.apache.org/jira/browse/MNG-6826 > Project: Maven > Issue Type: Improvement > Components: Bootstrap Build >Affects Versions: 3.6.3 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > Conditions to check for JDK8+ in FileSizeFormatTest test cases are obsolete > with the lift to JDK8. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7407) Introduce a ModelVersionProcessor component to make CI Friendly Versions pluggable
[ https://issues.apache.org/jira/browse/MNG-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527097#comment-17527097 ] Hudson commented on MNG-7407: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Introduce a ModelVersionProcessor component to make CI Friendly Versions > pluggable > -- > > Key: MNG-7407 > URL: https://issues.apache.org/jira/browse/MNG-7407 > Project: Maven > Issue Type: New Feature >Affects Versions: 3.8.4 >Reporter: Christoph Läubrich >Assignee: Michael Osipov >Priority: Major > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > > Currently the handling for https://maven.apache.org/maven-ci-friendly.html is > hard wired into maven. > For Tycho we like to replace/extend the default handling for this to supply > the user with some automatic derived values for some of the variables. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7428) Upgrade Maven Parent to 35
[ https://issues.apache.org/jira/browse/MNG-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527103#comment-17527103 ] Hudson commented on MNG-7428: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Upgrade Maven Parent to 35 > -- > > Key: MNG-7428 > URL: https://issues.apache.org/jira/browse/MNG-7428 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7413) Fix POM model documentation confusion on report plugins, distribution repository and profile build
[
https://issues.apache.org/jira/browse/MNG-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527113#comment-17527113
]
Hudson commented on MNG-7413:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Fix POM model documentation confusion on report plugins, distribution
> repository and profile build
> --
>
> Key: MNG-7413
> URL: https://issues.apache.org/jira/browse/MNG-7413
> Project: Maven
> Issue Type: Bug
> Components: Documentation: General, POM
>Affects Versions: 3.8.4
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> after upgrading Modello to 2.0.0, it detected following conflicts in POM
> documentation:
> {noformat}
> [warn] model class repository/org.apache.maven.model.Repository with tagName
> repository gets duplicate anchorName class_repository, conflicting with model
> class repository/org.apache.maven.model.DeploymentRepository
> [warn] model class plugin/org.apache.maven.model.ReportPlugin with tagName
> plugin gets duplicate anchorName class_plugin, conflicting with model class
> plugin/org.apache.maven.model.Plugin
> [warn] model class build/org.apache.maven.model.BuildBase with tagName build
> gets duplicate anchorName class_build, conflicting with model class
> build/org.apache.maven.model.Build
> {noformat}
> it corresponds to:
> - "repository" link
> https://maven.apache.org/ref/3.6.3/maven-model/maven.html#class_repository is
> the same for project/repository, but also for
> distributionManagement/repository which does not have same fields
> - "plugin" link
> https://maven.apache.org/ref/3.6.3/maven-model/maven.html#class_plugin is the
> same from build plugin but also report plugin which does not have same fields
> - 'build" link
> https://maven.apache.org/ref/3.6.3/maven-model/maven.html#class_build is for
> build and profile/build
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7385) Improve documentation on repository metadata
[ https://issues.apache.org/jira/browse/MNG-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527091#comment-17527091 ] Hudson commented on MNG-7385: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Improve documentation on repository metadata > > > Key: MNG-7385 > URL: https://issues.apache.org/jira/browse/MNG-7385 > Project: Maven > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 3.8.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > > working on MNG-7375, it is clear that current documentation on repository > metadata (I wrote in 2020...) needs more details: > https://maven.apache.org/ref/3.8.4/maven-repository-metadata/index.html > and there is one specific question to document: given > [org.apache.maven.artifact.repository.metadata.GroupRepositoryMetadata|https://maven.apache.org/ref/3.8.4/maven-compat/apidocs/org/apache/maven/artifact/repository/metadata/GroupRepositoryMetadata.html] > has been put in maven-compat, it seems it means that plugins information is > considered "compat" only and will be removed in the future > => we need to confirm and document (for example by marking some generated > classes as deprecated) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7347) SessionScoped beans should be singletons for a given session
[ https://issues.apache.org/jira/browse/MNG-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527086#comment-17527086 ] Hudson commented on MNG-7347: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > SessionScoped beans should be singletons for a given session > > > Key: MNG-7347 > URL: https://issues.apache.org/jira/browse/MNG-7347 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.4 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-5561) Plugin relocation loses configuration
[
https://issues.apache.org/jira/browse/MNG-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527083#comment-17527083
]
Hudson commented on MNG-5561:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Plugin relocation loses configuration
> -
>
> Key: MNG-5561
> URL: https://issues.apache.org/jira/browse/MNG-5561
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.1.1
>Reporter: Julien CARSIQUE
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
> Attachments: screenshot-1.png
>
>
> Hi,
> Applying a relocation on a plugin seems to lose its configuration.
> In the following sample, I relocated "nuxeo-distribution-tools" to
> "ant-assembly-maven-plugin" and the missing configured parameter is
> "buildFile". The relocation itself went well but the execution fails because
> of a missing parameter.
> {code:title=~/.m2/repository/org/nuxeo/build/nuxeo-distribution-tools/2.0-SNAPSHOT/nuxeo-distribution-tools-2.0-SNAPSHOT.pom}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> org.nuxeo.build
> nuxeo-distribution-tools
> 2.0-SNAPSHOT
> maven-plugin
> Nuxeo Distribution Build
> Assemble Nuxeo distributions
>
>
> ant-assembly-maven-plugin
>
>
> {code}
> {code:title=executed POM extract}
>
>
>
> org.nuxeo.build
>
> nuxeo-distribution-tools
>
>
>
>
> assemble
> package
>
>
> src/main/assemble/assembly.xml
>
>
> build
>
>
>
>
>
>
> {code}
> Here is the diff between an "mvn package -X" with nuxeo-distribution-tools
> (ie: with relocation; line starting with "<") and another one with
> ant-assembly-maven-plugin (ie: without relocation; line starting with ">"):
> {noformat}< [DEBUG] Dependency collection stats:
> {ConflictMarker.analyzeTime=1, ConflictMarker.markTime=0,
> ConflictMarker.nodeCount=72, ConflictIdSorter.graphTime=0,
> ConflictIdSorter.topsortTime=0, ConflictIdSorter.conflictIdCount=34,
> ConflictIdSorter.conflictIdCycleCount=0, ConflictResolver.totalTime=1,
> ConflictResolver.conflictItemCount=71,
> DefaultDependencyCollector.collectTime=10,
> DefaultDependencyCollector.transformTime=2}
> > [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=1,
> > ConflictMarker.markTime=0, ConflictMarker.nodeCount=72,
> > ConflictIdSorter.graphTime=0, ConflictIdSorter.topsortTime=0,
> > ConflictIdSorter.conflictIdCount=34,
> > ConflictIdSorter.conflictIdCycleCount=0, ConflictResolver.totalTime=2,
> > ConflictResolver.conflictItemCount=71,
> > DefaultDependencyCollector.collectTime=65,
> > DefaultDependencyCollector.transformTime=3}
> ---
> < [DEBUG] Created new class realm
> plugin>org.nuxeo.build:nuxeo-distribution-tools:2.0-SNAPSHOT
> < [DEBUG] Importing foreign packages into class realm
> plugin>org.nuxeo.build:nuxeo-distribution-tools:2.0-SNAPSHOT
> > [DEBUG] Created new class realm
> > plugin>org.nuxeo.build:ant-assembly-maven-plugin:2.0-SNAPSHOT
> > [DEBUG] Importing foreign packages into class realm
> > plugin>org.nuxeo.build:ant-assembly-maven-plugin:2.0-SNAPSHOT
> ---
> < [DEBUG] Populating class realm
> plugin>org.nuxeo.build:nuxeo-distribution-tools:2.0-SNAPSHOT
> > [DEBUG] Populating class realm
> > plugin>org.nuxeo.build:ant-assembly-maven-plugin:2.0-SNAPSHOT
> ---
> < [DEBUG] Configuring mojo
> org.nuxeo.build:ant-assembly-maven-plugin:2.0-SNAPSHOT:build from plugin
> realm
> ClassRealm[plugin>org.nuxeo.build:nuxeo-distribution-tools:2.0-SNAPSHOT,
> parent: sun.misc.Launcher$AppClassLoader@591ce4fe]
> > [DEBUG] Configuring mojo
> > org.nuxeo.build:ant-assembly-maven-plugin:2.0-SNAPSHOT:build from plugin
> > realm
> > ClassRealm[plugin>org.nuxeo.build:ant-assembly-maven-plugin:2.0-SNAPSHOT,
> > parent: sun.misc.Launcher$AppClassLoader@77fe0d66]
> ---
> > [DEBUG] (f) buildFile =
> > /home/julien/ws-ssd/nuxeo/nuxeo-distribution/nuxeo-distribution-resources/src/main/assemble/assembly.xml{noformat}
> The last line highlights the missing parameter.
> Indeed, it seems that in case of a relocation, all the "Parameter" Mojo
> fields take their default value (or none) whereas the "Component" fields are
> still properly injected.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7402) BuildListCalculator never detaches the classloader
[ https://issues.apache.org/jira/browse/MNG-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527100#comment-17527100 ] Hudson commented on MNG-7402: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > BuildListCalculator never detaches the classloader > -- > > Key: MNG-7402 > URL: https://issues.apache.org/jira/browse/MNG-7402 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.4 >Reporter: Christoph Läubrich >Assignee: Michael Osipov >Priority: Major > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > > https://github.com/apache/maven/blob/6b607109d3ce045106924139e96705fe7c42172e/maven-core/src/main/java/org/apache/maven/lifecycle/internal/BuildListCalculator.java#L63 > Her there is attachToThread called but never detached. This seems to be a > leak, at least the threads current contextclassloader is never restored. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7219) [Regression] plexus-cipher missing from transitive dependencies
[
https://issues.apache.org/jira/browse/MNG-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527067#comment-17527067
]
Hudson commented on MNG-7219:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> [Regression] plexus-cipher missing from transitive dependencies
> ---
>
> Key: MNG-7219
> URL: https://issues.apache.org/jira/browse/MNG-7219
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.8.2
>Reporter: Nils Breunese
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.8.3, 4.0.0-alpha-1, 4.0.0
>
>
> I have a project that uses
> {{org.apache.maven.plugin-testing:maven-plugin-testing-harness:3.3.0}} for
> testing a Maven plugin.
> After upgrading the project’s Maven dependencies from Maven 3.8.1 to 3.8.2 I
> got this error message when running tests:
> {code}
> Error injecting:
> org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher
> java.lang.NoClassDefFoundError:
> org/sonatype/plexus/components/cipher/PlexusCipher... 117 more
> {code}
> {{PlexusCipher}} is a class in the {{plexus-cipher}} artifact, which is a
> transitive dependency of {{maven-core}} 3.8.1:
> {code}
> [INFO] org.example:plexus-cipher-mystery:jar:1.0-SNAPSHOT
> [INFO] \- org.apache.maven:maven-core:jar:3.8.1:compile
> [INFO]+- org.apache.maven:maven-model:jar:3.8.1:compile
> [INFO]+- org.apache.maven:maven-settings:jar:3.8.1:compile
> [INFO]+- org.apache.maven:maven-settings-builder:jar:3.8.1:compile
> [INFO]| +- org.codehaus.plexus:plexus-interpolation:jar:1.25:compile
> [INFO]| \- org.sonatype.plexus:plexus-sec-dispatcher:jar:1.4:compile
> [INFO]| \- org.sonatype.plexus:plexus-cipher:jar:1.4:compile
> [INFO]+- org.apache.maven:maven-builder-support:jar:3.8.1:compile
> (…snip…)
> {code}
> But {{plexus-cipher}} is not a transitive dependency of {{maven-core}} 3.8.2:
> {code}
> [INFO] org.example:plexus-cipher-mystery:jar:1.0-SNAPSHOT
> [INFO] \- org.apache.maven:maven-core:jar:3.8.2:compile
> [INFO]+- org.apache.maven:maven-model:jar:3.8.2:compile
> [INFO]+- org.apache.maven:maven-settings:jar:3.8.2:compile
> [INFO]+- org.apache.maven:maven-settings-builder:jar:3.8.2:compile
> [INFO]| +- org.codehaus.plexus:plexus-interpolation:jar:1.25:compile
> [INFO]| \- org.sonatype.plexus:plexus-sec-dispatcher:jar:1.4:compile
> [INFO]+- org.apache.maven:maven-builder-support:jar:3.8.2:compile
> (…snip…)
> {code}
> Both {{maven-core}} 3.8.1 and 3.8.2 have a transitive dependency on
> {{org.sonatype.plexus:plexus-sec-dispatcher:jar:1.4}}. When using
> {{maven-core}} 3.8.1 {{plexus-sec-dispatcher}} has a dependency on
> plexus-cipher, but when using {{maven-core}} 3.8.2 it doesn’t.
> The [{{pom.xml}} of
> {{plexus-sec-dispatcher:1.4}}|https://search.maven.org/artifact/org.sonatype.plexus/plexus-sec-dispatcher/1.4/jar]
> indeed declares a dependency on {{plexus-cipher}} 1.4, but it’s not there
> when depending on {{maven-core}} 3.8.2.
> This regression was [confirmed by Michael Osipov on the Maven Users mailing
> list|https://lists.apache.org/thread.html/r7f5a62fd35dc6698c8f7097734f7c4acf4bb657d6c721e8a7bc76b8c%40%3Cusers.maven.apache.org%3E].
> He mentioned that it was caused by commit
> 41efc134a9067b58a5ab01e9b8b05d2bd84a94f0, which was done for MNG-6886
> ("upgrade plexus-cipher to 1.8 and update changed groupId"). A global
> exclusion was performed, but not all affected modules were properly updated
> (so the change wasn't complete):
> {code}
> [DEBUG] org.apache.maven:maven-settings-builder:jar:3.8.2
> [DEBUG]org.apache.maven:maven-builder-support:jar:3.8.2:compile
> [DEBUG]javax.inject:javax.inject:jar:1:compile
> [DEBUG]org.codehaus.plexus:plexus-interpolation:jar:1.25:compile
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:3.2.1:compile
> [DEBUG]org.apache.maven:maven-settings:jar:3.8.2:compile
> [DEBUG]org.sonatype.plexus:plexus-sec-dispatcher:jar:1.4:compile
> (exclusions managed from [org.sonatype.plexus:plexus-cipher:*:*])
> [DEBUG]junit:junit:jar:4.12:test
> [DEBUG] org.hamcrest:hamcrest-core:jar:1.3:test (scope managed from
> compile) (version managed from 1.3)
> [INFO] org.apache.maven:maven-settings-builder:jar:3.8.2
> [INFO] +- org.apache.maven:maven-builder-support:jar:3.8.2:compile
> [INFO] +- javax.inject:javax.inject:jar:1:compile
> [INFO] +- org.codehaus.plexus:plexus-interpolation:jar:1.25:compile
> [INFO] +- org.codehaus.plexus:plexus-utils:jar:3.2.1:compile
> [INFO] +- org.apache.maven:maven-settings:jar:3.8.2:compile
> [INFO] +- org.sonatype.plexus:plexus-sec-dispatcher:jar:1.4:compile
> [INFO] \- junit:junit:jar:4.12:test
>
[jira] [Commented] (MNG-7019) Notify also at start when profile is missing
[ https://issues.apache.org/jira/browse/MNG-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527109#comment-17527109 ] Hudson commented on MNG-7019: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Notify also at start when profile is missing > > > Key: MNG-7019 > URL: https://issues.apache.org/jira/browse/MNG-7019 > Project: Maven > Issue Type: Sub-task > Components: Profiles >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > This will implement the first task on the list. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7156) Parallel build can cause issues between clean and forked goals
[
https://issues.apache.org/jira/browse/MNG-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527078#comment-17527078
]
Hudson commented on MNG-7156:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Parallel build can cause issues between clean and forked goals
> --
>
> Key: MNG-7156
> URL: https://issues.apache.org/jira/browse/MNG-7156
> Project: Maven
> Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> Running {{mvn -T12 clean verify -Papache-release}} From
> [https://github.com/apache/jackrabbit-filevault] leads to various exceptions
> caused by the invocation of the {{clean}} goal.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-5180) Versioning's snapshot version list is not included in metadata merge
[ https://issues.apache.org/jira/browse/MNG-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527101#comment-17527101 ] Hudson commented on MNG-5180: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Versioning's snapshot version list is not included in metadata merge > -- > > Key: MNG-5180 > URL: https://issues.apache.org/jira/browse/MNG-5180 > Project: Maven > Issue Type: Bug >Affects Versions: 3.0.3 >Reporter: Noam Y. Tenne >Assignee: Michael Osipov >Priority: Major > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > Attachments: MavenMetadataSnapshotVersionsMergeTest.java > > > Versioning#snapshotVersions is not being merged when using Metadata#merge. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7068) Active dependency management for Google Guice/Guava
[ https://issues.apache.org/jira/browse/MNG-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527107#comment-17527107 ] Hudson commented on MNG-7068: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Active dependency management for Google Guice/Guava > --- > > Key: MNG-7068 > URL: https://issues.apache.org/jira/browse/MNG-7068 > Project: Maven > Issue Type: Improvement > Components: Dependencies >Affects Versions: 3.6.3 >Reporter: Boris Unckel >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > The current pom includes com.google.inject:guice with the default transitive > dependency of com.google.guava:guava. Guava has declared several > dependencies, which are not needed at runtime. Only > com.google.guava:failureaccess is needed. > The proposal is first to add com.google.guava:guava to the excludes of guice. > Second guava and failureaccess shall be added as direct dependencies. > This has two advantages: Downstream projects only get the needed dependencies > and the version of guava can be independently set. > The runtime dependencies for Guava are explained in the last section of the > [README|https://github.com/google/guava/tree/v30.1] "Important Warnings" #3 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7380) Don't log non-threadsafe warning if only building a single module
[
https://issues.apache.org/jira/browse/MNG-7380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527088#comment-17527088
]
Hudson commented on MNG-7380:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Don't log non-threadsafe warning if only building a single module
> -
>
> Key: MNG-7380
> URL: https://issues.apache.org/jira/browse/MNG-7380
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
>Affects Versions: 3.8.4
>Reporter: Falko Modler
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> When building a _single_ module (via {{-f}}, {{-pl}} or simply cd'ing into
> it) with e.g. {{-T1C}} in {{.mvn/maven.config}} logs a warning if a
> non-threadsafe mojo is executed, e.g.:
> {noformat}
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that have goals not marked *
> [WARNING] * as @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in
> code-with-quarkus:
> [WARNING] io.quarkus.platform:quarkus-maven-plugin:2.6.1.Final
> [WARNING] Enable debug to see more precisely which goals are not marked
> @threadSafe.
> [WARNING] *
> {noformat}
> This is unnecessary noise because with only a single module there can never
> be a concurrency issue, no matter how many threads are enabled.
> Maven should check if it's building only one module before logging this
> warning.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7247) Upgrade Maven Resolver to 1.7.2
[ https://issues.apache.org/jira/browse/MNG-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527105#comment-17527105 ] Hudson commented on MNG-7247: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Upgrade Maven Resolver to 1.7.2 > --- > > Key: MNG-7247 > URL: https://issues.apache.org/jira/browse/MNG-7247 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories, Dependencies >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > h1. Release Notes - Maven Resolver - Version 1.7.0 > h2. Bug > * [MRESOLVER-153] - resolver-status.properties file is corrupted due to > concurrent writes > * [MRESOLVER-171] - Resolver fails when compiled on Java 9+ and run on > Java 8 due to JDK API breakage > h2. New Feature > * [MRESOLVER-90] - HTML content in POM: Maven should validate content > before storing in local repo > * [MRESOLVER-145] - Introduce more SyncContext implementations > h2. Improvement > * [MRESOLVER-104] - maven-resolver-demo-maven-plugin uses reserved > artifactId > * [MRESOLVER-147] - Upgrade to Java 8 > * [MRESOLVER-148] - Use vanilla Guice 4 instead of forked Guice 3 > * [MRESOLVER-156] - Active dependency management for Google Guice/Guava > * [MRESOLVER-168] - add DEBUG message when downloading an artifact from > repositories > h2. Task > * [MRESOLVER-141] - Review index-based access to collections > * [MRESOLVER-151] - Enforce a checksum policy to be provided explicitly > * [MRESOLVER-154] - Move SyncContextFactory interface to SPI module > * [MRESOLVER-155] - Make TrackingFileManager member of > DefaultUpdateCheckManager > * [MRESOLVER-158] - Simplify SimpleDigest class > * [MRESOLVER-159] - Mark singleton components as Sisu Singletons > * [MRESOLVER-160] - Deprecate ServiceLocator > * [MRESOLVER-162] - Restore binary compatibility broken by MRESOLVER-154 > * [MRESOLVER-170] - Deprecate org.eclipse.aether.spi.log > * [MRESOLVER-172] - Make TrackingFileManager shared singleton component > * [MRESOLVER-173] - Drop deprecated AetherModule > * [MRESOLVER-174] - Use all bindings in UTs and tests > * [MRESOLVER-175] - Drop SyncContextFactory delegates in favor of a > selector approach > * [MRESOLVER-177] - Move pre-/post-processing of metadata from > ResolveTask to DefaultMetadataResolver > h1. Release Notes - Maven Resolver - Version 1.7.1 > h2. Bug > * [MRESOLVER-96] - Dependency Injection fails after upgrading to Maven > 3.6.2 > h2. Improvement > * [MRESOLVER-103] - Replace deprecated HttpClient classes > h2. Task > * [MRESOLVER-183] - Don't require optional dependencies for Redisson > * [MRESOLVER-184] - Destroy Redisson semaphores if not used anymore > * [MRESOLVER-186] - Update Maven version in Resolver Demo Snippets > h2. Dependency upgrade > * [MRESOLVER-185] - Upgrade Redisson to 3.15.6 > h1. Release Notes - Maven Resolver - Version 1.7.2 > h2. Sub-task > * [MRESOLVER-198] - Replace assert by simpler but equivalent calls > * [MRESOLVER-199] - Java 8 improvements > * [MRESOLVER-200] - Simplify conditions with the same result and avoid > extra validations > * [MRESOLVER-201] - Make variables final whenever possible > * [MRESOLVER-202] - Use isEmpty() instead length() <= 0 > h2. Bug > * [MRESOLVER-189] - Using semaphore-redisson followed by rwlock-redisson > on many parallel build of the same project triggers redisson error > h2. Improvement > * [MRESOLVER-193] - Properly type lock key names in Redis > * [MRESOLVER-197] - Minors improvements (umbrella) > h2. Task > * [MRESOLVER-152] - Perform null checks when interface contracts require > it > * [MRESOLVER-188] - Improve documentation on using the named locks with > redis/hazelcast (umbrella) > * [MRESOLVER-190] - [Regression] Revert MRESOLVER-184 > * [MRESOLVER-191] - Document how to analyze lock issues > * [MRESOLVER-196] - Document named locks configuration options > h1. Release Notes - Maven Resolver - Version 1.7.3 > h2. Sub-task > * [MRESOLVER-203] - Remove presized arrays in favor of empty ones > h2. Improvement > * [MRESOLVER-204] - Add a SessionData#computeIfAbsent method > * [MRESOLVER-214] - Remove clirr configuration > h2. Task > * [MRESOLVER-219] - Implement NamedLock with advisory file locking > * [MRESOLVER-227] - Refactor NamedLockFactorySelector to a managed > component > * [MRESOLVER-232] - Make SimpleNamedLockFactorySelector logic reusable -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-6960) Use RuntimeInformation instead of reading properties
[ https://issues.apache.org/jira/browse/MNG-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527102#comment-17527102 ] Hudson commented on MNG-6960: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Use RuntimeInformation instead of reading properties > > > Key: MNG-6960 > URL: https://issues.apache.org/jira/browse/MNG-6960 > Project: Maven > Issue Type: Improvement > Components: Core >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7384) Upgrade Maven JAR Plugin to 3.2.2
[ https://issues.apache.org/jira/browse/MNG-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527089#comment-17527089 ] Hudson commented on MNG-7384: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Upgrade Maven JAR Plugin to 3.2.2 > - > > Key: MNG-7384 > URL: https://issues.apache.org/jira/browse/MNG-7384 > Project: Maven > Issue Type: Dependency upgrade >Affects Versions: 3.8.4 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0 > > > This version fixes an important issue with the order of JAR entries. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7235) Speed improvements when calculating the sorted project graph
[
https://issues.apache.org/jira/browse/MNG-7235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527074#comment-17527074
]
Hudson commented on MNG-7235:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Speed improvements when calculating the sorted project graph
>
>
> Key: MNG-7235
> URL: https://issues.apache.org/jira/browse/MNG-7235
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.8.3, 4.0.0-alpha-1, 4.0.0
>
>
> The {{DefaultProjectDependencyGraph#getSortedProjects}} method is really
> inefficient and some data could be easily cached to have a performance boost.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-6727) Using version range in parent and CI Friendly Version fails
[
https://issues.apache.org/jira/browse/MNG-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527094#comment-17527094
]
Hudson commented on MNG-6727:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Using version range in parent and CI Friendly Version fails
> ---
>
> Key: MNG-6727
> URL: https://issues.apache.org/jira/browse/MNG-6727
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation, POM, Reactor and Workspace
>Affects Versions: 3.5.2, 3.6.1, 3.6.2, 3.6.3
>Reporter: Tom Kiemes
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> We would like to pass a [version
> range|https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html] to
> the parent which should be possible since 3.5.0
> At the same time, we would like to use [CI friendly
> versions|https://maven.apache.org/maven-ci-friendly.html] for the artifact
> itself.
> Both on their own work well, but combined they don't.
> {{}}
> {{http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> }}{{xsi:schemaLocation="[http://maven.apache.org/POM/4.0.0]
> [http://maven.apache.org/xsd/maven-4.0.0.xsd];>}}
> {{ 4.0.0}}
> {{ }}
> {{ org.springframework.boot}}
> {{ spring-boot-starter-parent}}
> {{ [2.1,3.0)}}
> {{ }}
> {{ com.example}}
> {{ test}}
> {{ ${revision}}}
> {{ pom}}
> {{ }}
> {{ 0.0.1}}
> {{ }}
> {{}}
>
> The resulting error is:
> {{The project com.example:test:${revision} (/Users/d045390/scratch/test.pom)
> has 1 error}}
> {{[ERROR] Version must be a constant @ line 13, column 12}}
>
> Changing the version range of the parent to a fixed version e.g.
> \{{2.1.5.Release}}, building works.
> Changing the artifact version from ${revision} to a fixed version e.g. 0.0.1
> without using the {{properties}} works as well.
> So it somehow must be the combination of both features which are actually not
> really related or am I missing something?
> PS: I left the modules out for abbreviation purpose. The pom itself can still
> be used to reproduced
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-6399) Lift JDK minimum to JDK 8
[ https://issues.apache.org/jira/browse/MNG-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527104#comment-17527104 ] Hudson commented on MNG-6399: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Lift JDK minimum to JDK 8 > - > > Key: MNG-6399 > URL: https://issues.apache.org/jira/browse/MNG-6399 > Project: Maven > Issue Type: Task >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > I would like to lift the minimum of Maven Core to JDK 8 (I think it's time).. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7417) Several classes do not set properties properly for building requests
[
https://issues.apache.org/jira/browse/MNG-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527099#comment-17527099
]
Hudson commented on MNG-7417:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Several classes do not set properties properly for building requests
>
>
> Key: MNG-7417
> URL: https://issues.apache.org/jira/browse/MNG-7417
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Inheritance and Interpolation
>Affects Versions: 3.8.4
>Reporter: Michael Osipov
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
> Attachments: log.txt
>
>
> A sample case for this bug is {{DefaultArtifactDescriptorReader}}:
> When Resolver needs to resolve a transitive dependency it consults Maven
> Resolver Provider to create data. Here the properties of the repository
> system session are not properly passed with their respective scopes down to
> the model building request. When a POM now needs needs to be interpolated,
> the interpolation can fail.
> For long time Maven, unfortunately, promoted user properties to system
> properties making the available everywhere (expect this to be cleaned up in
> Maven 4). A prime example where this is broken:
> {{DefaultModelVersionProcessor}} uses for some strange reason system
> properties although CI Friendly Versions are user properties only. Fixing
> this component with:
> {noformat}
> ---
> a/maven-model-builder/src/main/java/org/apache/maven/model/interpolation/DefaultModelVersionProcessor.java
> +++
> b/maven-model-builder/src/main/java/org/apache/maven/model/interpolation/DefaultModelVersionProcessor.java
> @@ -52,17 +52,17 @@ public boolean isValidProperty( String property )
> @Override
> public void overwriteModelProperties( Properties modelProperties,
> ModelBuildingRequest request )
> {
> -if ( request.getSystemProperties().containsKey( REVISION_PROPERTY ) )
> +if ( request.getUserProperties().containsKey( REVISION_PROPERTY ) )
> {
> -modelProperties.put( REVISION_PROPERTY,
> request.getSystemProperties().get( REVISION_PROPERTY ) );
> +modelProperties.put( REVISION_PROPERTY,
> request.getUserProperties().get( REVISION_PROPERTY ) );
> }
> -if ( request.getSystemProperties().containsKey( CHANGELIST_PROPERTY
> ) )
> +if ( request.getUserProperties().containsKey( CHANGELIST_PROPERTY ) )
> {
> -modelProperties.put( CHANGELIST_PROPERTY,
> request.getSystemProperties().get( CHANGELIST_PROPERTY ) );
> +modelProperties.put( CHANGELIST_PROPERTY,
> request.getUserProperties().get( CHANGELIST_PROPERTY ) );
> }
> -if ( request.getSystemProperties().containsKey( SHA1_PROPERTY ) )
> +if ( request.getUserProperties().containsKey( SHA1_PROPERTY ) )
> {
> -modelProperties.put( SHA1_PROPERTY,
> request.getSystemProperties().get( SHA1_PROPERTY ) );
> +modelProperties.put( SHA1_PROPERTY,
> request.getUserProperties().get( SHA1_PROPERTY ) );
> }
> }
> {noformat}
> and running ITs makes several of them fail:
> {noformat}
> ...
> mng6090 CIFriendly.itShouldResolveTheDependenciesWithBuildConsumer() FAILURE
> (10.4 s)
> mng6090 CIFriendly.itShouldResolveTheDependenciesWithoutBuildConsumer()
> FAILURE (1.2 s)
> ...
> mng5895
> CIFriendlyUsageWithProperty.itShouldResolveTheDependenciesWithBuildConsumer()
> FAILURE (0.5 s)
> mng5895
> CIFriendlyUsageWithProperty.itShouldResolveTheDependenciesWithoutBuildConsumer()
> FAILURE (0.5 s)
> ...
> {noformat}
> The reason is simple:
> {code:java}
> modelRequest.setSystemProperties( toProperties(
> session.getUserProperties(),
>
> session.getSystemProperties() ) );
> {code}
> Properties from user are not available. The are likely other usecases
> affected by this bug.
> Yet another problem is that plugins which resolve dependencies, e.g.,
> MASSEMBLY will also fail even if this bug is fixed since they rely on an old
> version of the Maven Resolver Provider and don't use provided scope to use
> the fixed one from Maven Core. This is a separate problem to be solved.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MNG-7164) Add constructor MojoExecutionException(Throwable)
[ https://issues.apache.org/jira/browse/MNG-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527073#comment-17527073 ] Hudson commented on MNG-7164: - Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/ > Add constructor MojoExecutionException(Throwable) > - > > Key: MNG-7164 > URL: https://issues.apache.org/jira/browse/MNG-7164 > Project: Maven > Issue Type: New Feature > Components: Plugin API > Environment: Apache Maven 3.8.1 > (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) > Maven home: C:\Java\apache-maven-3.8.1\bin\.. > Java version: 1.8.0_261, vendor: Oracle Corporation, runtime: C:\Program > Files\Java\jdk1.8.0_261\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" >Reporter: Gary D. Gregory >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.8.3, 4.0.0-alpha-1, 4.0.0 > > > Sometimes I have nothing additional to say in a message, I just want to > propagate the Throwable. -- This message was sent by Atlassian Jira (v8.20.7#820007)
