[jira] [Commented] (MNG-7214) Bad transitive dependency parent from CDI API
[ https://issues.apache.org/jira/browse/MNG-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404962#comment-17404962 ] Delany commented on MNG-7214: - [~khmarbaise] we maintain a Maven plugin that depends on Maven core. The issue surfaces when building it under 3.8.2 and the flatten-maven-plugin configured with flattenDependencyMode=all > Bad transitive dependency parent from CDI API > - > > Key: MNG-7214 > URL: https://issues.apache.org/jira/browse/MNG-7214 > Project: Maven > Issue Type: Bug > Components: Core >Affects Versions: 3.8.2 >Reporter: Delany >Priority: Major > > Maven core has these dependencies > > [INFO] | +- org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.3.4:compile > > [INFO] | | \- javax.enterprise:cdi-api:jar:1.0:compile > > [INFO] | | \- javax.annotation:jsr250-api:jar:1.0:compile > Then although javax.enterprise:cdi-api is in javax namespace, its > parent is > > > > org.jboss.weld > > weld-api-parent > > 1.0 > > ../parent/pom.xml > > > Attempting to resolve will fail > Blocked mirror for repositories: > [[repository.jboss.org|http://repository.jboss.org/] > ([http://repository.jboss.org/maven2], default, releases), > [snapshots.jboss.org|http://snapshots.jboss.org/] > ([http://snapshots.jboss.org/maven2], default, snapshots), > [oss.sonatype.org/jboss-snapshots|http://oss.sonatype.org/jboss-snapshots] > ([http://oss.sonatype.org/content/repositories/jboss-snapshots], default, > snapshots)] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-jlink-plugin] dependabot[bot] commented on pull request #69: Bump mockito-core from 3.10.0 to 3.12.1
dependabot[bot] commented on pull request #69: URL: https://github.com/apache/maven-jlink-plugin/pull/69#issuecomment-906076681 Superseded by #70. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] dependabot[bot] opened a new pull request #70: Bump mockito-core from 3.10.0 to 3.12.4
dependabot[bot] opened a new pull request #70: URL: https://github.com/apache/maven-jlink-plugin/pull/70 Bumps [mockito-core](https://github.com/mockito/mockito) from 3.10.0 to 3.12.4. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v3.12.4 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.4 2021-08-25 - https://github.com/mockito/mockito/compare/v3.12.3...v3.12.4";>1 commit(s) by Rafael Winterhalter No notable improvements. No pull requests (issues) were referenced from commits. v3.12.3 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.3 2021-08-24 - https://github.com/mockito/mockito/compare/v3.12.2...v3.12.3";>9 commit(s) by Rafael Winterhalter Fix implementation of proxy mock maker for toString and add additional unit tests. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2405";>#2405)](https://github-redirect.dependabot.com/mockito/mockito/pull/2405";>mockito/mockito#2405) Avoid cache breakage [(https://github-redirect.dependabot.com/mockito/mockito/issues/2402";>#2402)](https://github-redirect.dependabot.com/mockito/mockito/pull/2402";>mockito/mockito#2402) Add a limited mock maker that is based only on the java.lang.reflect.Proxy utility [(https://github-redirect.dependabot.com/mockito/mockito/issues/2397";>#2397)](https://github-redirect.dependabot.com/mockito/mockito/pull/2397";>mockito/mockito#2397) v3.12.2 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.2 2021-08-24 - https://github.com/mockito/mockito/compare/v3.12.1...v3.12.2";>2 commit(s) by Dmitry Vyazelenko, dependabot[bot] Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2399";>#2399 : Adds defaultAnswer to the MockitoMockKey to distinguish the mock types, i.e. to separate mocks from spies otherwise spy type is reused for a mock or vice versa. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2400";>#2400)](https://github-redirect.dependabot.com/mockito/mockito/pull/2400";>mockito/mockito#2400) Sporadic mock verification failures related to hashCode/equals on 3.12.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2399";>#2399)](https://github-redirect.dependabot.com/mockito/mockito/issues/2399";>mockito/mockito#2399) Bump versions.errorprone from 2.8.1 to 2.9.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2396";>#2396)](https://github-redirect.dependabot.com/mockito/mockito/pull/2396";>mockito/mockito#2396) v3.12.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.1 2021-08-20 - https://github.com/mockito/mockito/compare/v3.12.0...v3.12.1";>2 commit(s) by Tim van der Lippe, dependabot[bot] Fix verifyNoMoreInteractions inOrder invocations for spies [(https://github-redirect.dependabot.com/mockito/mockito/issues/2395";>#2395)](https://github-redirect.dependabot.com/mockito/mockito/pull/2395";>mockito/mockito#2395) Regression with InOrder verification after https://github-redirect.dependabot.com/mockito/mockito/issues/2369";>#2369 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2394";>#2394)](https://github-redirect.dependabot.com/mockito/mockito/issues/2394";>mockito/mockito#2394) Bump versions.bytebuddy from 1.11.12 to 1.11.13 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2393";>#2393)](https://github-redirect.dependabot.com/mockito/mockito/pull/2393";>mockito/mockito#2393) v3.12.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.0 2021-08-19 - https://github.com/mockito/mockito/compare/v3.11.2...v3.12.0";>31 commit(s) by EugeneLesnov, Lars Vogel, Logan Rosen, Rafael Winterhalter, Rob Pridham, Tim van der Lippe, dependabot[bot], saurabh7248 Add checks for sealed types [(https://github-redirect.dependabot.com/mockito/mockito/issues/2392";>#2392)](https://github-redirect.dependabot.com/mockito/mockito/pull/2392";>mockito/mockito#2392) Bump versions.bytebuddy from 1.11.10 to 1.11.12 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2388";>#2388)](https://github-redirect.dependabot.com/mockito/mockito/pull/2388";>mockito/mockito#2388) Bump versions.bytebuddy from 1.11.9 to 1.11.10 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2387";>#2387)](https://github-redirect.dependabot.com/mockito/mockito/pull/2387";>mockito/mockito#2387) Bump versions.errorprone from 2.8.0 to 2.8.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2386";>#2386)](https://github-redirect.dependabot.com/mockito/mockito/pull/2386";>mockito/mockito#2386) Update StaticMockTest to use unified verify m
[GitHub] [maven-jlink-plugin] dependabot[bot] closed pull request #69: Bump mockito-core from 3.10.0 to 3.12.1
dependabot[bot] closed pull request #69: URL: https://github.com/apache/maven-jlink-plugin/pull/69 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MJAVADOC-689) When I run "javadoc:fix" , I get an error .
si changxu created MJAVADOC-689: --- Summary: When I run "javadoc:fix" , I get an error . Key: MJAVADOC-689 URL: https://issues.apache.org/jira/browse/MJAVADOC-689 Project: Maven Javadoc Plugin Issue Type: Bug Components: fix Affects Versions: 3.3.0 Reporter: si changxu Attachments: Log.zip My English is not good, Sorry `(*>﹏<*)′ When I run "javadoc:fix" , I get an error . I try debug . In "AbstractFixJavadocMojo.java" LineNumber : 2945 . I find a method named "getFullClirrGoal " . and in this return a string like "org.codehaus.mojo:clirr-maven-plugin:2.2.2:check" I think the problem may be in the version "2.2.2" so i change it to "2.8" , and it`s work . So I want to know is a bug or I made a mistake. I put the log in attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MJAVADOC-689) When I run "javadoc:fix" , I get an error .
[ https://issues.apache.org/jira/browse/MJAVADOC-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] si changxu updated MJAVADOC-689: Attachment: Log.zip > When I run "javadoc:fix" , I get an error . > --- > > Key: MJAVADOC-689 > URL: https://issues.apache.org/jira/browse/MJAVADOC-689 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: fix >Affects Versions: 3.3.0 >Reporter: si changxu >Priority: Major > Attachments: Log.zip > > > My English is not good, Sorry `(*>﹏<*)′ > When I run "javadoc:fix" , I get an error . > I try debug . > In "AbstractFixJavadocMojo.java" LineNumber : 2945 . > I find a method named "getFullClirrGoal " . and in this return a string like > "org.codehaus.mojo:clirr-maven-plugin:2.2.2:check" > I think the problem may be in the version "2.2.2" so i change it to "2.8" , > and it`s work . > So I want to know is a bug or I made a mistake. > I put the log in attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-dependency-plugin] dependabot[bot] commented on pull request #157: Bump mockito-core from 2.28.2 to 3.12.3
dependabot[bot] commented on pull request #157: URL: https://github.com/apache/maven-dependency-plugin/pull/157#issuecomment-905905356 Superseded by #158. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-plugin] dependabot[bot] closed pull request #157: Bump mockito-core from 2.28.2 to 3.12.3
dependabot[bot] closed pull request #157: URL: https://github.com/apache/maven-dependency-plugin/pull/157 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request #158: Bump mockito-core from 2.28.2 to 3.12.4
dependabot[bot] opened a new pull request #158: URL: https://github.com/apache/maven-dependency-plugin/pull/158 Bumps [mockito-core](https://github.com/mockito/mockito) from 2.28.2 to 3.12.4. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v3.12.4 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.4 2021-08-25 - https://github.com/mockito/mockito/compare/v3.12.3...v3.12.4";>1 commit(s) by Rafael Winterhalter No notable improvements. No pull requests (issues) were referenced from commits. v3.12.3 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.3 2021-08-24 - https://github.com/mockito/mockito/compare/v3.12.2...v3.12.3";>9 commit(s) by Rafael Winterhalter Fix implementation of proxy mock maker for toString and add additional unit tests. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2405";>#2405)](https://github-redirect.dependabot.com/mockito/mockito/pull/2405";>mockito/mockito#2405) Avoid cache breakage [(https://github-redirect.dependabot.com/mockito/mockito/issues/2402";>#2402)](https://github-redirect.dependabot.com/mockito/mockito/pull/2402";>mockito/mockito#2402) Add a limited mock maker that is based only on the java.lang.reflect.Proxy utility [(https://github-redirect.dependabot.com/mockito/mockito/issues/2397";>#2397)](https://github-redirect.dependabot.com/mockito/mockito/pull/2397";>mockito/mockito#2397) v3.12.2 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.2 2021-08-24 - https://github.com/mockito/mockito/compare/v3.12.1...v3.12.2";>2 commit(s) by Dmitry Vyazelenko, dependabot[bot] Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2399";>#2399 : Adds defaultAnswer to the MockitoMockKey to distinguish the mock types, i.e. to separate mocks from spies otherwise spy type is reused for a mock or vice versa. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2400";>#2400)](https://github-redirect.dependabot.com/mockito/mockito/pull/2400";>mockito/mockito#2400) Sporadic mock verification failures related to hashCode/equals on 3.12.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2399";>#2399)](https://github-redirect.dependabot.com/mockito/mockito/issues/2399";>mockito/mockito#2399) Bump versions.errorprone from 2.8.1 to 2.9.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2396";>#2396)](https://github-redirect.dependabot.com/mockito/mockito/pull/2396";>mockito/mockito#2396) v3.12.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.1 2021-08-20 - https://github.com/mockito/mockito/compare/v3.12.0...v3.12.1";>2 commit(s) by Tim van der Lippe, dependabot[bot] Fix verifyNoMoreInteractions inOrder invocations for spies [(https://github-redirect.dependabot.com/mockito/mockito/issues/2395";>#2395)](https://github-redirect.dependabot.com/mockito/mockito/pull/2395";>mockito/mockito#2395) Regression with InOrder verification after https://github-redirect.dependabot.com/mockito/mockito/issues/2369";>#2369 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2394";>#2394)](https://github-redirect.dependabot.com/mockito/mockito/issues/2394";>mockito/mockito#2394) Bump versions.bytebuddy from 1.11.12 to 1.11.13 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2393";>#2393)](https://github-redirect.dependabot.com/mockito/mockito/pull/2393";>mockito/mockito#2393) v3.12.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.0 2021-08-19 - https://github.com/mockito/mockito/compare/v3.11.2...v3.12.0";>31 commit(s) by EugeneLesnov, Lars Vogel, Logan Rosen, Rafael Winterhalter, Rob Pridham, Tim van der Lippe, dependabot[bot], saurabh7248 Add checks for sealed types [(https://github-redirect.dependabot.com/mockito/mockito/issues/2392";>#2392)](https://github-redirect.dependabot.com/mockito/mockito/pull/2392";>mockito/mockito#2392) Bump versions.bytebuddy from 1.11.10 to 1.11.12 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2388";>#2388)](https://github-redirect.dependabot.com/mockito/mockito/pull/2388";>mockito/mockito#2388) Bump versions.bytebuddy from 1.11.9 to 1.11.10 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2387";>#2387)](https://github-redirect.dependabot.com/mockito/mockito/pull/2387";>mockito/mockito#2387) Bump versions.errorprone from 2.8.0 to 2.8.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2386";>#2386)](https://github-redirect.dependabot.com/mockito/mockito/pull/2386";>mockito/mockito#2386) Update StaticMockTest to use unified v
[jira] [Created] (MRESOLVER-191) Document how to analyze lock issues
Michael Osipov created MRESOLVER-191: Summary: Document how to analyze lock issues Key: MRESOLVER-191 URL: https://issues.apache.org/jira/browse/MRESOLVER-191 Project: Maven Resolver Issue Type: Task Components: Resolver Affects Versions: 1.7.1 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 1.7.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MDEPLOY-286) Wrong documentation for format of altDeploymentRepository
[
https://issues.apache.org/jira/browse/MDEPLOY-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404681#comment-17404681
]
Michael Osipov commented on MDEPLOY-286:
Please see: MDEPLOY-265 and MDEPLOY-279.
> Wrong documentation for format of altDeploymentRepository
> -
>
> Key: MDEPLOY-286
> URL: https://issues.apache.org/jira/browse/MDEPLOY-286
> Project: Maven Deploy Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-M1
>Reporter: Roland Illig
>Priority: Minor
>
> [https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html] says:
> > Format: id::layout::url
> As of version 3.0.0-M1, this is wrong. The format is now simply `id::url`.
> The old format is no longer accepted.
> While here, the documentation for {{altReleaseDeploymentRepository}} and
> {{altSnapshotDeploymentRepository}}. could be extended to contain the same
> information as the {{altDeploymentRepository}}. The current documentation is
> not completely clear on whether the syntax of these 3 properties follows the
> same rules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MRESOLVER-190) [Regression] Revert MRESOLVER-184
[ https://issues.apache.org/jira/browse/MRESOLVER-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-190: - Description: As it turns out the deletion of the semaphore results in a race condition when multiple Maven instances are trying to use the semaphore. The result is they lock up until the timeout is reached and the build fails. See also: https://github.com/redisson/redisson/issues/3728 (was: As it turns out the deletion of the semaphore results in a race condition when multiple Maven instances are trying to use the semaphore. The result is they lock up. See also: https://github.com/redisson/redisson/issues/3728) > [Regression] Revert MRESOLVER-184 > - > > Key: MRESOLVER-190 > URL: https://issues.apache.org/jira/browse/MRESOLVER-190 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Affects Versions: 1.7.1 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.7.2 > > > As it turns out the deletion of the semaphore results in a race condition > when multiple Maven instances are trying to use the semaphore. The result is > they lock up until the timeout is reached and the build fails. See also: > https://github.com/redisson/redisson/issues/3728 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-7214) Bad transitive dependency parent from CDI API
[ https://issues.apache.org/jira/browse/MNG-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404651#comment-17404651 ] Karl Heinz Marbaise commented on MNG-7214: -- Can you give please more context about the problem. If the dependency is part of Maven core why is it a problem on user side? > Bad transitive dependency parent from CDI API > - > > Key: MNG-7214 > URL: https://issues.apache.org/jira/browse/MNG-7214 > Project: Maven > Issue Type: Bug > Components: Core >Affects Versions: 3.8.2 >Reporter: Delany >Priority: Major > > Maven core has these dependencies > > [INFO] | +- org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.3.4:compile > > [INFO] | | \- javax.enterprise:cdi-api:jar:1.0:compile > > [INFO] | | \- javax.annotation:jsr250-api:jar:1.0:compile > Then although javax.enterprise:cdi-api is in javax namespace, its > parent is > > > > org.jboss.weld > > weld-api-parent > > 1.0 > > ../parent/pom.xml > > > Attempting to resolve will fail > Blocked mirror for repositories: > [[repository.jboss.org|http://repository.jboss.org/] > ([http://repository.jboss.org/maven2], default, releases), > [snapshots.jboss.org|http://snapshots.jboss.org/] > ([http://snapshots.jboss.org/maven2], default, snapshots), > [oss.sonatype.org/jboss-snapshots|http://oss.sonatype.org/jboss-snapshots] > ([http://oss.sonatype.org/content/repositories/jboss-snapshots], default, > snapshots)] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MRELEASE-1068) Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on project XXXXXX: could not perform a local checkout
[
https://issues.apache.org/jira/browse/MRELEASE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404609#comment-17404609
]
Leonardo edited comment on MRELEASE-1068 at 8/25/21, 5:13 PM:
--
Worked! (y)
{quote}maven-release-plugin - 3.0.0-M4 without specify the maven-scm-plugin
(/){quote}
{quote}
maven-release-plugin - 2.5.3 +maven-scm-plugin - 1.11.3 (x)
{quote}
was (Author: vendrusculo):
Worked! (y)
{quote}{{}}
{{ org.apache.maven.plugins}}
{{ maven-release-plugin}}
{{ 3.0.0-M4}}
{{ }}
{{ false}}
{{ true}}
{{ }}
{{ }}
{{ }}
{{ org.apache.maven.plugins}}
{{ maven-scm-plugin}}
{{ 1.11.2}}
{{ }}
{{ connection}}
{{ }}
{{ }}
{quote}
> Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on
> project XX: could not perform a local checkout
> --
>
> Key: MRELEASE-1068
> URL: https://issues.apache.org/jira/browse/MRELEASE-1068
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.5.3
> Environment: Plugin Configuration:
>
> org.apache.maven.plugins
> maven-release-plugin
> 2.5.3
>
> false
> true
>
>
>Reporter: Leonardo
>Priority: Minor
> Labels: Jenkins, checkout, local
>
> I'm trying to use a Jenkins pipeline to release a library and I'm getting
> this error:
> Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on
> project XXX: could not perform a local checkout
> As far I identify the problem in fact is beacuse the workDirectory has an "@"
> in the project base dir (/var/lib/jenkins/workspace/xx@2/) because I'm
> running the job in an agent into another agent, but, I was also able to
> reproduce it on Windows machine moving my project base dir to a directory
> with @ in the path name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MRELEASE-1068) Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on project XXXXXX: could not perform a local checkout
[ https://issues.apache.org/jira/browse/MRELEASE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRELEASE-1068. Fix Version/s: (was: waiting-for-feedback) Resolution: Not A Problem > Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on > project XX: could not perform a local checkout > -- > > Key: MRELEASE-1068 > URL: https://issues.apache.org/jira/browse/MRELEASE-1068 > Project: Maven Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.5.3 > Environment: Plugin Configuration: > > org.apache.maven.plugins > maven-release-plugin > 2.5.3 > > false > true > > >Reporter: Leonardo >Priority: Minor > Labels: Jenkins, checkout, local > > I'm trying to use a Jenkins pipeline to release a library and I'm getting > this error: > Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on > project XXX: could not perform a local checkout > As far I identify the problem in fact is beacuse the workDirectory has an "@" > in the project base dir (/var/lib/jenkins/workspace/xx@2/) because I'm > running the job in an agent into another agent, but, I was also able to > reproduce it on Windows machine moving my project base dir to a directory > with @ in the path name. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRELEASE-1068) Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on project XXXXXX: could not perform a local checkout
[
https://issues.apache.org/jira/browse/MRELEASE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404609#comment-17404609
]
Leonardo commented on MRELEASE-1068:
Worked! (y)
{quote}{{}}
{{ org.apache.maven.plugins}}
{{ maven-release-plugin}}
{{ 3.0.0-M4}}
{{ }}
{{ false}}
{{ true}}
{{ }}
{{ }}
{{ }}
{{ org.apache.maven.plugins}}
{{ maven-scm-plugin}}
{{ 1.11.2}}
{{ }}
{{ connection}}
{{ }}
{{ }}
{quote}
> Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on
> project XX: could not perform a local checkout
> --
>
> Key: MRELEASE-1068
> URL: https://issues.apache.org/jira/browse/MRELEASE-1068
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.5.3
> Environment: Plugin Configuration:
>
> org.apache.maven.plugins
> maven-release-plugin
> 2.5.3
>
> false
> true
>
>
>Reporter: Leonardo
>Priority: Minor
> Labels: Jenkins, checkout, local
> Fix For: waiting-for-feedback
>
>
> I'm trying to use a Jenkins pipeline to release a library and I'm getting
> this error:
> Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on
> project XXX: could not perform a local checkout
> As far I identify the problem in fact is beacuse the workDirectory has an "@"
> in the project base dir (/var/lib/jenkins/workspace/xx@2/) because I'm
> running the job in an agent into another agent, but, I was also able to
> reproduce it on Windows machine moving my project base dir to a directory
> with @ in the path name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MJAVADOC-686) NullPointerException if is not defined
[
https://issues.apache.org/jira/browse/MJAVADOC-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJAVADOC-686.
---
Assignee: Robert Scholte
Resolution: Cannot Reproduce
I've to reproduce it with the provided configuration in a minimum POM, but it
succeeds, as expected.
> NullPointerException if is not defined
>
>
> Key: MJAVADOC-686
> URL: https://issues.apache.org/jira/browse/MJAVADOC-686
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
> Environment: Intellij Idea Ultimate 2021.1.3, Windows 10
>Reporter: Dustin
>Assignee: Robert Scholte
>Priority: Major
>
> If a used dependency has a not defined URL in its pom.xml, this plugin throws
> a NPE when trying to build it with goal javadoc:javadoc.
>
> Stacktrace:
> {code:java}
> [ERROR] Error while creating javadoc report: null
> java.lang.NullPointerException
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.isValidJavadocLink
> (AbstractJavadocMojo.java:6694)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getDependenciesLinks
> (AbstractJavadocMojo.java:6483)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.collectLinks
> (AbstractJavadocMojo.java:3396)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addLinkArguments
> (AbstractJavadocMojo.java:4362)
> at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addStandardDocletOptions
> (AbstractJavadocMojo.java:5589)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
> (AbstractJavadocMojo.java:2170)
> at org.apache.maven.plugins.javadoc.JavadocReport.generate
> (JavadocReport.java:135)
> at org.apache.maven.plugins.javadoc.JavadocReport.doExecute
> (JavadocReport.java:324)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.execute
> (AbstractJavadocMojo.java:2010)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
> at org.codehaus.classworlds.Launcher.main (Launcher.java:47){code}
> Configuration:
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.3.0
>
> protected
> true
>
>
> https://javadoc.io/doc/org.jetbrains/annotations/19.0.0/
>
> https://logging.apache.org/log4j/2.x/log4j-api/apidocs/
>
> false
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven] hboutemy commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
hboutemy commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695930776 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment: thank you all for the detailed explanation: I learned something new and interesting today :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPOM-266) Incorrect message with missing property "project.build.outputTimestamp"
[
https://issues.apache.org/jira/browse/MPOM-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404588#comment-17404588
]
Herve Boutemy commented on MPOM-266:
given the value will be inherited because it is necessary for ASF Parent POM
reproducible release, yes, enforcer won't emit any message
> Incorrect message with missing property "project.build.outputTimestamp"
> ---
>
> Key: MPOM-266
> URL: https://issues.apache.org/jira/browse/MPOM-266
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-24
>Reporter: Konrad Windszus
>Priority: Major
>
> The check introduced with MPOM-255 emits the following error message:
> bq. The property "project.build.outputTimestamp" must be set on the reactor's
> root pom.xml to make the build reproducible. Further information at
> "https://maven.apache.org/guides/mini/guide-reproducible-builds.html";.
> Having the property on the reactor's root pom.xml is not sufficient though in
> case reactor root != parent.
> Consider the following project structure
> {code}
> reactor root (has no parent)
> + module1 (has parent: parent)
> + parent (has parent: asf-parent)
> {code}
> In this case setting the property in {{reactor root}} is not enough, as each
> module's effective pom.xml must contain the property
> {{project.build.outputTimestamp}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MRESOLVER-190) [Regression] Revert MRESOLVER-184
Michael Osipov created MRESOLVER-190: Summary: [Regression] Revert MRESOLVER-184 Key: MRESOLVER-190 URL: https://issues.apache.org/jira/browse/MRESOLVER-190 Project: Maven Resolver Issue Type: Task Components: Resolver Affects Versions: 1.7.1 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 1.7.2 As it turns out the deletion of the semaphore results in a race condition when multiple Maven instances are trying to use the semaphore. The result is they lock up. See also: https://github.com/redisson/redisson/issues/3728 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRELEASE-1068) Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on project XXXXXX: could not perform a local checkout
[ https://issues.apache.org/jira/browse/MRELEASE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404586#comment-17404586 ] Michael Osipov commented on MRELEASE-1068: -- Upgrade Maven Release and Maven SCM first. > Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on > project XX: could not perform a local checkout > -- > > Key: MRELEASE-1068 > URL: https://issues.apache.org/jira/browse/MRELEASE-1068 > Project: Maven Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.5.3 > Environment: Plugin Configuration: > > org.apache.maven.plugins > maven-release-plugin > 2.5.3 > > false > true > > >Reporter: Leonardo >Priority: Minor > Labels: Jenkins, checkout, local > Fix For: waiting-for-feedback > > > I'm trying to use a Jenkins pipeline to release a library and I'm getting > this error: > Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on > project XXX: could not perform a local checkout > As far I identify the problem in fact is beacuse the workDirectory has an "@" > in the project base dir (/var/lib/jenkins/workspace/xx@2/) because I'm > running the job in an agent into another agent, but, I was also able to > reproduce it on Windows machine moving my project base dir to a directory > with @ in the path name. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven] qweek commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
qweek commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695641759 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment:  Setup: - run on Oracle JDK 1.8.0.201 on Windows and Linux - use 100 jar files with different size from 3 KB to 90 MB, total size 474 MB - read in single thread, calculate hash for each file and total checksum - separate folder for each algorithm to avoid disk cache testing - 100 rounds to minimize CPU interference from external loads - time in seconds, candle body is 25-75 percentile, shadow is min/max values Results: - xxHash (5th column) shows stable time about 3-4 sec on both Windows and Linux platforms - xxHash with Memory Mapped buffer (last column) gives another small gain on Linux, useful on CI - SHA-256 about 4 times slower with a difference of 10 seconds even on this small test P.S. also tested 5157 files with total size 2.6 GB, difference between xxHash and SHA-256 was about 1.5-2 min -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MDEPLOY-286) Wrong documentation for format of altDeploymentRepository
Roland Illig created MDEPLOY-286:
Summary: Wrong documentation for format of altDeploymentRepository
Key: MDEPLOY-286
URL: https://issues.apache.org/jira/browse/MDEPLOY-286
Project: Maven Deploy Plugin
Issue Type: Bug
Affects Versions: 3.0.0-M1
Reporter: Roland Illig
[https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html] says:
> Format: id::layout::url
As of version 3.0.0-M1, this is wrong. The format is now simply `id::url`. The
old format is no longer accepted.
While here, the documentation for {{altReleaseDeploymentRepository}} and
{{altSnapshotDeploymentRepository}}. could be extended to contain the same
information as the {{altDeploymentRepository}}. The current documentation is
not completely clear on whether the syntax of these 3 properties follows the
same rules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MJAVADOC-688) When I run "javadoc:fix" , I get an error .
[ https://issues.apache.org/jira/browse/MJAVADOC-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404524#comment-17404524 ] si changxu commented on MJAVADOC-688: - I have finished translating > When I run "javadoc:fix" , I get an error . > --- > > Key: MJAVADOC-688 > URL: https://issues.apache.org/jira/browse/MJAVADOC-688 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: fix >Affects Versions: 3.3.0 > Environment: java version 11.0.12 > maven version 3.6.3 >Reporter: si changxu >Priority: Major > Attachments: Log.zip > > > My English is not good, Sorry `(*>﹏<*)′ > When I run "javadoc:fix" , I get an error . > I try debug . > In "AbstractFixJavadocMojo.java" LineNumber : 2945 . > I find a method named "getFullClirrGoal " . and in this return a string like > "org.codehaus.mojo:clirr-maven-plugin:2.2.2:check" > I think the problem may be in the version "2.2.2" so i change it to "2.8" , > and it`s work . > So I want to know is a bug or I made a mistake. > I put the log in attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MJAVADOC-688) When I run "javadoc:fix" , I get an error .
[ https://issues.apache.org/jira/browse/MJAVADOC-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] si changxu updated MJAVADOC-688: Description: My English is not good, Sorry `(*>﹏<*)′ When I run "javadoc:fix" , I get an error . I try debug . In "AbstractFixJavadocMojo.java" LineNumber : 2945 . I find a method named "getFullClirrGoal " . and in this return a string like "org.codehaus.mojo:clirr-maven-plugin:2.2.2:check" I think the problem may be in the version "2.2.2" so i change it to "2.8" , and it`s work . So I want to know is a bug or I made a mistake. I put the log in attachment. was: 执行 javadoc:fix 时出现错误 , 简单 debug 一下发现大概在 AbstractFixJavadocMojo.java 的 2945 行 getFullClirrGoal 方法中获取 clirrVersion 版本为 2.2.2. 将其改为 2.8 后错误消失; 希望将 CLIRR_MAVEN_PLUGIN_VERSION 更新到 2.8 > When I run "javadoc:fix" , I get an error . > --- > > Key: MJAVADOC-688 > URL: https://issues.apache.org/jira/browse/MJAVADOC-688 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: fix >Affects Versions: 3.3.0 > Environment: java version 11.0.12 > maven version 3.6.3 >Reporter: si changxu >Priority: Major > Attachments: Log.zip > > > My English is not good, Sorry `(*>﹏<*)′ > When I run "javadoc:fix" , I get an error . > I try debug . > In "AbstractFixJavadocMojo.java" LineNumber : 2945 . > I find a method named "getFullClirrGoal " . and in this return a string like > "org.codehaus.mojo:clirr-maven-plugin:2.2.2:check" > I think the problem may be in the version "2.2.2" so i change it to "2.8" , > and it`s work . > So I want to know is a bug or I made a mistake. > I put the log in attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MJAVADOC-688) When I run "javadoc:fix" , I get an error .
[ https://issues.apache.org/jira/browse/MJAVADOC-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] si changxu updated MJAVADOC-688: Summary: When I run "javadoc:fix" , I get an error . (was: When I run Javadoc: fix, I get an error .) > When I run "javadoc:fix" , I get an error . > --- > > Key: MJAVADOC-688 > URL: https://issues.apache.org/jira/browse/MJAVADOC-688 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: fix >Affects Versions: 3.3.0 > Environment: java version 11.0.12 > maven version 3.6.3 >Reporter: si changxu >Priority: Major > Attachments: Log.zip > > > 执行 javadoc:fix 时出现错误 , > 简单 debug 一下发现大概在 AbstractFixJavadocMojo.java 的 2945 行 > getFullClirrGoal 方法中获取 clirrVersion 版本为 2.2.2. 将其改为 2.8 后错误消失; > 希望将 CLIRR_MAVEN_PLUGIN_VERSION 更新到 2.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MJAVADOC-688) When I run Javadoc: fix, I get an error .
[ https://issues.apache.org/jira/browse/MJAVADOC-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] si changxu updated MJAVADOC-688: Summary: When I run Javadoc: fix, I get an error . (was: 执行 javadoc:fix 时出现错误) > When I run Javadoc: fix, I get an error . > - > > Key: MJAVADOC-688 > URL: https://issues.apache.org/jira/browse/MJAVADOC-688 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: fix >Affects Versions: 3.3.0 > Environment: java version 11.0.12 > maven version 3.6.3 >Reporter: si changxu >Priority: Major > Attachments: Log.zip > > > 执行 javadoc:fix 时出现错误 , > 简单 debug 一下发现大概在 AbstractFixJavadocMojo.java 的 2945 行 > getFullClirrGoal 方法中获取 clirrVersion 版本为 2.2.2. 将其改为 2.8 后错误消失; > 希望将 CLIRR_MAVEN_PLUGIN_VERSION 更新到 2.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-compiler-plugin] dependabot[bot] opened a new pull request #64: Bump mockito-core from 2.28.2 to 3.12.3
dependabot[bot] opened a new pull request #64: URL: https://github.com/apache/maven-compiler-plugin/pull/64 Bumps [mockito-core](https://github.com/mockito/mockito) from 2.28.2 to 3.12.3. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v3.12.3 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.3 2021-08-24 - https://github.com/mockito/mockito/compare/v3.12.2...v3.12.3";>9 commit(s) by Rafael Winterhalter Fix implementation of proxy mock maker for toString and add additional unit tests. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2405";>#2405)](https://github-redirect.dependabot.com/mockito/mockito/pull/2405";>mockito/mockito#2405) Avoid cache breakage [(https://github-redirect.dependabot.com/mockito/mockito/issues/2402";>#2402)](https://github-redirect.dependabot.com/mockito/mockito/pull/2402";>mockito/mockito#2402) Add a limited mock maker that is based only on the java.lang.reflect.Proxy utility [(https://github-redirect.dependabot.com/mockito/mockito/issues/2397";>#2397)](https://github-redirect.dependabot.com/mockito/mockito/pull/2397";>mockito/mockito#2397) v3.12.2 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.2 2021-08-24 - https://github.com/mockito/mockito/compare/v3.12.1...v3.12.2";>2 commit(s) by Dmitry Vyazelenko, dependabot[bot] Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2399";>#2399 : Adds defaultAnswer to the MockitoMockKey to distinguish the mock types, i.e. to separate mocks from spies otherwise spy type is reused for a mock or vice versa. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2400";>#2400)](https://github-redirect.dependabot.com/mockito/mockito/pull/2400";>mockito/mockito#2400) Sporadic mock verification failures related to hashCode/equals on 3.12.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2399";>#2399)](https://github-redirect.dependabot.com/mockito/mockito/issues/2399";>mockito/mockito#2399) Bump versions.errorprone from 2.8.1 to 2.9.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2396";>#2396)](https://github-redirect.dependabot.com/mockito/mockito/pull/2396";>mockito/mockito#2396) v3.12.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.1 2021-08-20 - https://github.com/mockito/mockito/compare/v3.12.0...v3.12.1";>2 commit(s) by Tim van der Lippe, dependabot[bot] Fix verifyNoMoreInteractions inOrder invocations for spies [(https://github-redirect.dependabot.com/mockito/mockito/issues/2395";>#2395)](https://github-redirect.dependabot.com/mockito/mockito/pull/2395";>mockito/mockito#2395) Regression with InOrder verification after https://github-redirect.dependabot.com/mockito/mockito/issues/2369";>#2369 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2394";>#2394)](https://github-redirect.dependabot.com/mockito/mockito/issues/2394";>mockito/mockito#2394) Bump versions.bytebuddy from 1.11.12 to 1.11.13 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2393";>#2393)](https://github-redirect.dependabot.com/mockito/mockito/pull/2393";>mockito/mockito#2393) v3.12.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 3.12.0 2021-08-19 - https://github.com/mockito/mockito/compare/v3.11.2...v3.12.0";>31 commit(s) by EugeneLesnov, Lars Vogel, Logan Rosen, Rafael Winterhalter, Rob Pridham, Tim van der Lippe, dependabot[bot], saurabh7248 Add checks for sealed types [(https://github-redirect.dependabot.com/mockito/mockito/issues/2392";>#2392)](https://github-redirect.dependabot.com/mockito/mockito/pull/2392";>mockito/mockito#2392) Bump versions.bytebuddy from 1.11.10 to 1.11.12 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2388";>#2388)](https://github-redirect.dependabot.com/mockito/mockito/pull/2388";>mockito/mockito#2388) Bump versions.bytebuddy from 1.11.9 to 1.11.10 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2387";>#2387)](https://github-redirect.dependabot.com/mockito/mockito/pull/2387";>mockito/mockito#2387) Bump versions.errorprone from 2.8.0 to 2.8.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2386";>#2386)](https://github-redirect.dependabot.com/mockito/mockito/pull/2386";>mockito/mockito#2386) Update StaticMockTest to use unified verify method [(https://github-redirect.dependabot.com/mockito/mockito/issues/2385";>#2385)](https://github-redirect.dependabot.com/mockito/mockito/pull/2385";>mockito/mockito#2385) Reorder InjectMock Javadoc to fit the order of injection [(https://github-redirect.dependabot.com/mockito/mockito/issues/2383";>#2383)](https://github-redir
[GitHub] [maven-compiler-plugin] dependabot[bot] closed pull request #62: Bump mockito-core from 2.28.2 to 3.12.1
dependabot[bot] closed pull request #62: URL: https://github.com/apache/maven-compiler-plugin/pull/62 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-compiler-plugin] dependabot[bot] commented on pull request #62: Bump mockito-core from 2.28.2 to 3.12.1
dependabot[bot] commented on pull request #62: URL: https://github.com/apache/maven-compiler-plugin/pull/62#issuecomment-905534391 Superseded by #64. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPOM-266) Incorrect message with missing property "project.build.outputTimestamp"
[
https://issues.apache.org/jira/browse/MPOM-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1740#comment-1740
]
Konrad Windszus commented on MPOM-266:
--
If the value is inherited the enforcer would not emit the message!
> Incorrect message with missing property "project.build.outputTimestamp"
> ---
>
> Key: MPOM-266
> URL: https://issues.apache.org/jira/browse/MPOM-266
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-24
>Reporter: Konrad Windszus
>Priority: Major
>
> The check introduced with MPOM-255 emits the following error message:
> bq. The property "project.build.outputTimestamp" must be set on the reactor's
> root pom.xml to make the build reproducible. Further information at
> "https://maven.apache.org/guides/mini/guide-reproducible-builds.html";.
> Having the property on the reactor's root pom.xml is not sufficient though in
> case reactor root != parent.
> Consider the following project structure
> {code}
> reactor root (has no parent)
> + module1 (has parent: parent)
> + parent (has parent: asf-parent)
> {code}
> In this case setting the property in {{reactor root}} is not enough, as each
> module's effective pom.xml must contain the property
> {{project.build.outputTimestamp}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MJAVADOC-688) 执行 javadoc:fix 时出现错误
[ https://issues.apache.org/jira/browse/MJAVADOC-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MJAVADOC-688. --- Resolution: Incomplete Try in English. > 执行 javadoc:fix 时出现错误 > > > Key: MJAVADOC-688 > URL: https://issues.apache.org/jira/browse/MJAVADOC-688 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: fix >Affects Versions: 3.3.0 > Environment: java version 11.0.12 > maven version 3.6.3 >Reporter: si changxu >Priority: Major > Attachments: Log.zip > > > 执行 javadoc:fix 时出现错误 , > 简单 debug 一下发现大概在 AbstractFixJavadocMojo.java 的 2945 行 > getFullClirrGoal 方法中获取 clirrVersion 版本为 2.2.2. 将其改为 2.8 后错误消失; > 希望将 CLIRR_MAVEN_PLUGIN_VERSION 更新到 2.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRELEASE-1069) typo: it's
[ https://issues.apache.org/jira/browse/MRELEASE-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404368#comment-17404368 ] Maarten Mulders commented on MRELEASE-1069: --- Thanks for taking the time to report this. If you feel comfortable with it, feel free to submit a pull request against [maven-release-plugin/src/site/apt/usage.apt.vm|https://github.com/apache/maven-release/blob/master/maven-release-plugin/src/site/apt/usage.apt.vm] via GitHub. > typo: it's > -- > > Key: MRELEASE-1069 > URL: https://issues.apache.org/jira/browse/MRELEASE-1069 > Project: Maven Release Plugin > Issue Type: Bug > Components: documentation >Affects Versions: 3.0.0-M4 >Reporter: Roland Illig >Priority: Minor > > [http://maven.apache.org/maven-release/maven-release-plugin/usage.html] says: > > is deployed with it's documentation > It should rather be: > > is deployed with its documentation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MRELEASE-1069) typo: it's
Roland Illig created MRELEASE-1069: -- Summary: typo: it's Key: MRELEASE-1069 URL: https://issues.apache.org/jira/browse/MRELEASE-1069 Project: Maven Release Plugin Issue Type: Bug Components: documentation Affects Versions: 3.0.0-M4 Reporter: Roland Illig [http://maven.apache.org/maven-release/maven-release-plugin/usage.html] says: > is deployed with it's documentation It should rather be: > is deployed with its documentation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MJAVADOC-688) 执行 javadoc:fix 时出现错误
[ https://issues.apache.org/jira/browse/MJAVADOC-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] si changxu updated MJAVADOC-688: Attachment: Log.zip > 执行 javadoc:fix 时出现错误 > > > Key: MJAVADOC-688 > URL: https://issues.apache.org/jira/browse/MJAVADOC-688 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: fix >Affects Versions: 3.3.0 > Environment: java version 11.0.12 > maven version 3.6.3 >Reporter: si changxu >Priority: Major > Attachments: Log.zip > > > 执行 javadoc:fix 时出现错误 , > 简单 debug 一下发现大概在 AbstractFixJavadocMojo.java 的 2945 行 > getFullClirrGoal 方法中获取 clirrVersion 版本为 2.2.2. 将其改为 2.8 后错误消失; > 希望将 CLIRR_MAVEN_PLUGIN_VERSION 更新到 2.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MJAVADOC-688) 执行 javadoc:fix 时出现错误
si changxu created MJAVADOC-688: --- Summary: 执行 javadoc:fix 时出现错误 Key: MJAVADOC-688 URL: https://issues.apache.org/jira/browse/MJAVADOC-688 Project: Maven Javadoc Plugin Issue Type: Bug Components: fix Affects Versions: 3.3.0 Environment: java version 11.0.12 maven version 3.6.3 Reporter: si changxu 执行 javadoc:fix 时出现错误 , 简单 debug 一下发现大概在 AbstractFixJavadocMojo.java 的 2945 行 getFullClirrGoal 方法中获取 clirrVersion 版本为 2.2.2. 将其改为 2.8 后错误消失; 希望将 CLIRR_MAVEN_PLUGIN_VERSION 更新到 2.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven] qweek commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
qweek commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695641759 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment:  Setup: - run on Oracle JDK 1.8.0.201 on Windows and Linux - use 100 jar files with different size from 3 KB to 90 MB, total size 474 MB - read in single thread, calculate hash for each file and total checksum - separate folder for each algorithm to avoid disk cache testing - 100 rounds to minimize CPU interference from external loads - time in seconds, candle body is 25-75 percentile, shadow is min/max values Results: - xxHash shows stable time (3-4 sec) on both Windows and Linux platforms - xxHash with Memory Mapped buffer (XXMM) gives another small gain on Linux, useful on CI - SHA-256 about 4 times slower with a difference of 10 seconds even on this small test P.S. also tested 5157 files with total size 2.6 GB, difference between xxHash and SHA-256 was about 1.5-2 min -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRELEASE-1068) Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on project XXXXXX: could not perform a local checkout
[
https://issues.apache.org/jira/browse/MRELEASE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404347#comment-17404347
]
Leonardo commented on MRELEASE-1068:
I just remove the @2, renaming the directory and this is the partial log...
{{c:\Tools\JavaWorkspace\>mvn -f ./pom.xml -s ./settings.xml -X
--batch-mode -DpushChanges=false -DlocalCheckout=true
-DpreparationGoals=initialize release:perform}}
{{Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)}}
{{Maven home: C:\Tools\Java\maven-3.6.3\bin\..}}
{{Java version: 1.8.0_265, vendor: Amazon.com Inc., runtime:
C:\Tools\Java\jdk1.8.0_265\jre}}
{{Default locale: en_US, platform encoding: Cp1252}}
{{OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"}}
{{[DEBUG] Created new class realm maven.api}}
{{[DEBUG] Importing foreign packages into class realm maven.api}}
{{[DEBUG] Imported: javax.annotation.* < plexus.core}}
{{[DEBUG] Imported: javax.annotation.security.* < plexus.core}}
{{[DEBUG] Imported: javax.enterprise.inject.* < plexus.core}}
{{[DEBUG] Imported: javax.enterprise.util.* < plexus.core}}
{{[DEBUG] Imported: javax.inject.* < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.* < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.artifact < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.classrealm < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.cli < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.configuration < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.exception < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.execution < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.execution.scope < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.model < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.monitor < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.plugin < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.profiles < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.project < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.reporting < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.repository < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.rtinfo < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.settings < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.toolchain < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.usability < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.* < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.events < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core}}
{{[DEBUG] Imported: org.codehaus.classworlds < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.* < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.component < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.container < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.context < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.logging < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.personality < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser <
plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException <
plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer <
plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.* < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.artifact < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.collection < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.deployment < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.graph < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.impl < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.installation < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.metadata < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.repository < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.resolution < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.spi < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.transfer < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.version < plexus.core}}
{{[DEBUG] Imported: org.fusesource.jansi.* < plexus.core}}
{{[DEBUG] Imported
[jira] [Commented] (MRELEASE-1068) Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on project XXXXXX: could not perform a local checkout
[
https://issues.apache.org/jira/browse/MRELEASE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404346#comment-17404346
]
Leonardo commented on MRELEASE-1068:
{{c:\Tools\JavaWorkspace\@2>mvn -f ./pom.xml -s ./settings.xml -X
--batch-mode -DpushChanges=false -DlocalCheckout=true
-DpreparationGoals=initialize release:perform}}
{{Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)}}
{{Maven home: C:\Tools\Java\maven-3.6.3\bin\..}}
{{Java version: 1.8.0_265, vendor: Amazon.com Inc., runtime:
C:\Tools\Java\jdk1.8.0_265\jre}}
{{Default locale: en_US, platform encoding: Cp1252}}
{{OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"}}
{{[DEBUG] Created new class realm maven.api}}
{{[DEBUG] Importing foreign packages into class realm maven.api}}
{{[DEBUG] Imported: javax.annotation.* < plexus.core}}
{{[DEBUG] Imported: javax.annotation.security.* < plexus.core}}
{{[DEBUG] Imported: javax.enterprise.inject.* < plexus.core}}
{{[DEBUG] Imported: javax.enterprise.util.* < plexus.core}}
{{[DEBUG] Imported: javax.inject.* < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.* < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.artifact < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.classrealm < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.cli < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.configuration < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.exception < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.execution < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.execution.scope < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.model < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.monitor < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.plugin < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.profiles < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.project < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.reporting < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.repository < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.rtinfo < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.settings < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.toolchain < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.usability < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.* < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.events < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core}}
{{[DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core}}
{{[DEBUG] Imported: org.codehaus.classworlds < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.* < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.component < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.container < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.context < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.logging < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.personality < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser <
plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException <
plexus.core}}
{{[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer <
plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.* < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.artifact < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.collection < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.deployment < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.graph < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.impl < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.installation < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.metadata < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.repository < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.resolution < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.spi < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.transfer < plexus.core}}
{{[DEBUG] Imported: org.eclipse.aether.version < plexus.core}}
{{[DEBUG] Imported: org.fusesource.jansi.* < plexus.core}}
{{[DEBUG] Imported: org.slf4j.* < plexus.core}}
{{[DEBUG] Imported: org.slf4j.event.* < plexus.c
[GitHub] [maven-invoker] olamy merged pull request #20: Bump actions/setup-java from 2.2.0 to 2.3.0
olamy merged pull request #20: URL: https://github.com/apache/maven-invoker/pull/20 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] michael-o commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
michael-o commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695589792 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment: I have noticed this on Resolver with SHA-256 and SHA-512. Horribly slow. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] qweek commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
qweek commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695588531 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment: No cryptographic strength is required here, in terms of quality xxHash has Score 10 in SMHasher test suite and [no reported problems](https://github.com/rurban/smhasher). @hboutemy SHA-1, SHA-256, SHA-384, SHA-512 are also supported. Just to mention that on a large project you can save several seconds by using fast hash function. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] qweek commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
qweek commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695588531 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment: No cryptographic strength is required here, in terms of quality xxHash has Score 10 in SMHasher test suite and [no reported problems](https://github.com/rurban/smhasher). @hboutemy SHA-1, SHA-256, SHA-384, SHA-512 are also supported, just to mention that on a large project you can save several seconds just by using fast hash function. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] qweek commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
qweek commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695588531 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment: No cryptographic strength is required here, in terms of quality xxHash has Score 10 in SMHasher test suite and [no reported problems](https://github.com/rurban/smhasher). @hboutemy SHA-1, SHA-256, SHA-384, SHA-512 is also supported, just to mention that on a large project you can save several seconds just by using fast hash function. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-98) resolver ant task doesn't appear to obey dependencyManagement
[ https://issues.apache.org/jira/browse/MRESOLVER-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404279#comment-17404279 ] Michael Osipov commented on MRESOLVER-98: - Still waiting... > resolver ant task doesn't appear to obey dependencyManagement > - > > Key: MRESOLVER-98 > URL: https://issues.apache.org/jira/browse/MRESOLVER-98 > Project: Maven Resolver > Issue Type: Bug > Components: Ant Tasks >Affects Versions: ant-tasks-1.2.0 >Reporter: Jay Kahrman >Priority: Major > Fix For: waiting-for-feedback > > Time Spent: 10m > Remaining Estimate: 0h > > We have a dependency in our pom which has dependencies that don't specify an > upper bound to the version range. To avoid getting different versions in > every build we use a dependencyManagement section in the POM to lock down the > version. This works via the maven 3 CLI, and via the old ant-tasks utility we > were using (). The maven-resolver-ant-tasks jar doesn't appear to obey the > dependencyManagement section, however. > > I'm not sure is this is related to MRESOLVER-33 and/or MRESOLVER-10 and if > updating maven-resolver-ant-tasks to depend on Maven Resolver 1.4.0 would > solve the problem. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven] michael-o commented on pull request #526: [MNG-7129] Incremental build and shared cache feature
michael-o commented on pull request #526: URL: https://github.com/apache/maven/pull/526#issuecomment-905254458 > > Massive! I already see room for improvement. > > How long did it take to go from concept to production? > > 2 weeks for a PoC and a month for 1st working version in prod :) How many FTEs? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7138) Proper verify of plugin configuration Bean set method call
[
https://issues.apache.org/jira/browse/MNG-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404247#comment-17404247
]
Slawomir Jaranowski commented on MNG-7138:
--
Feature was introduced in MNG-5013 by [~bentmann]
> Proper verify of plugin configuration Bean set method call
> --
>
> Key: MNG-7138
> URL: https://issues.apache.org/jira/browse/MNG-7138
> Project: Maven
> Issue Type: Improvement
> Components: Integration Tests
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> When we use custom {{Bean}} as {{plugin}} parameter configuration, {{set}}
> method of {{Bean}} is only called for default value.
> Example:
> {code:java}
> public class MyMojo extends AbstractMojo
> {
>@Parameter
> private Bean beanParam;
> }
> {code}
> {code:java}
> public class Bean
> {
>private String field1;
>private String field2;
>public void set(String value) {
> this.field1 = value;
>}
> }
> {code}
>
> And configuration with fields name:
> {code:xml}
>
>
> value1
> value2
>
>
> {code}
> in this case {{Bean.set}} is not called.
>
> When we have:
> {code:xml}
>
>value
>
> {code}
> {{Bean.set}} is called.
>
> I will fix it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven] michael-o commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
michael-o commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695475230 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment: Note that xxHash by Yann Collet is non-cryptographic. I don't know whether it makes a difference here. I consider all SHA hashes as abysmally slow compared to xxHash and BLAKE3. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] maximilian-novikov-db commented on pull request #526: [MNG-7129] Incremental build and shared cache feature
maximilian-novikov-db commented on pull request #526: URL: https://github.com/apache/maven/pull/526#issuecomment-905250800 > Massive! I already see room for improvement. > How long did it take to go from concept to production? 2 weeks for a PoC and a month for 1st working version in prod :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] maximilian-novikov-db commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
maximilian-novikov-db commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695470401 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment: it's for xxHash which we found as the most fastest -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] maximilian-novikov-db commented on a change in pull request #526: [MNG-7129] Incremental build and shared cache feature
maximilian-novikov-db commented on a change in pull request #526: URL: https://github.com/apache/maven/pull/526#discussion_r695470401 ## File path: Documentation/CACHE-HOWTO.md ## @@ -0,0 +1,204 @@ + + +### Overview + +Cache configuration provides you additional control over incremental maven behavior. Follow it step by step to +understand how it works and figure out your optimal config + +### Minimal config + +Absolutely minimal config which enables incremental maven with local cache + +```xml + +http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="org:apache:maven:cache:config:v1 cache-config.xsd"> + + +true +XX Review comment: it's for xxHash which we found as a most fastest -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MENFORCER-397) allow no rules
[
https://issues.apache.org/jira/browse/MENFORCER-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Delany updated MENFORCER-397:
-
Description:
Allow no rules by adding property similar to
[http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#failIfNoTests]
Currently the execution fails
{quote}No rules are configured. Use the skip flag if you want to disable
execution.
{quote}
For some background, my strategy in dealing with lots of XML is to configure
plugin executions upfront with an id, goal, and default properties, and then
allow modules to populate them with the minimum e.g.
{code:java}
fail
enforce
true
warn
enforce
false
{code}
and then
{code:java}
warn
remote.name
Distribution profile invoked without setting a
remote.name: repositories may not be configured correctly
{code}
was:
Allow no rules by adding property similar to
[http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#failIfNoTests]
Currently the execution fails
{quote}No rules are configured. Use the skip flag if you want to disable
execution.
{quote}
For some background, my strategy in dealing with lots of XML is to configure
plugin executions upfront with an id, goal, and default properties, and then
allow modules to populate them with the minimum e.g.
{code:java}
fail
enforce
true
warn
enforce
true
{code}
and then
{code:java}
warn
remote.name
Distribution profile invoked without setting a
remote.name: repositories may not be configured correctly
{code}
> allow no rules
> --
>
> Key: MENFORCER-397
> URL: https://issues.apache.org/jira/browse/MENFORCER-397
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: Delany
>Priority: Minor
>
> Allow no rules by adding property similar to
> [http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#failIfNoTests]
> Currently the execution fails
> {quote}No rules are configured. Use the skip flag if you want to disable
> execution.
> {quote}
> For some background, my strategy in dealing with lots of XML is to configure
> plugin executions upfront with an id, goal, and default properties, and then
> allow modules to populate them with the minimum e.g.
> {code:java}
>
>
> fail
>
> enforce
>
>
> true
>
>
>
> warn
>
> enforce
>
>
> false
>
>
>
> {code}
> and then
> {code:java}
>
>
> warn
>
>
>
> remote.name
> Distribution profile invoked without setting a
> remote.name: repositories may not be configured correctly
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MENFORCER-397) allow no rules
Delany created MENFORCER-397:
Summary: allow no rules
Key: MENFORCER-397
URL: https://issues.apache.org/jira/browse/MENFORCER-397
Project: Maven Enforcer Plugin
Issue Type: Improvement
Components: Plugin
Affects Versions: 3.0.0
Reporter: Delany
Allow no rules by adding property similar to
[http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#failIfNoTests]
Currently the execution fails
{quote}No rules are configured. Use the skip flag if you want to disable
execution.
{quote}
For some background, my strategy in dealing with lots of XML is to configure
plugin executions upfront with an id, goal, and default properties, and then
allow modules to populate them with the minimum e.g.
{code:java}
fail
enforce
true
warn
enforce
true
{code}
and then
{code:java}
warn
remote.name
Distribution profile invoked without setting a
remote.name: repositories may not be configured correctly
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MPOM-266) Incorrect message with missing property "project.build.outputTimestamp"
[
https://issues.apache.org/jira/browse/MPOM-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404235#comment-17404235
]
Herve Boutemy commented on MPOM-266:
notice: more importantly, telling that the property must be set "to make the
build reproducible" is the "most wrong" part
the build is reproducible without the local property, by inheriting parent
value: adding a build-specific property will just adjust the value with more
sensible value (for people who care about timestamp in jar files)
> Incorrect message with missing property "project.build.outputTimestamp"
> ---
>
> Key: MPOM-266
> URL: https://issues.apache.org/jira/browse/MPOM-266
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-24
>Reporter: Konrad Windszus
>Priority: Major
>
> The check introduced with MPOM-255 emits the following error message:
> bq. The property "project.build.outputTimestamp" must be set on the reactor's
> root pom.xml to make the build reproducible. Further information at
> "https://maven.apache.org/guides/mini/guide-reproducible-builds.html";.
> Having the property on the reactor's root pom.xml is not sufficient though in
> case reactor root != parent.
> Consider the following project structure
> {code}
> reactor root (has no parent)
> + module1 (has parent: parent)
> + parent (has parent: asf-parent)
> {code}
> In this case setting the property in {{reactor root}} is not enough, as each
> module's effective pom.xml must contain the property
> {{project.build.outputTimestamp}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MPOM-266) Incorrect message with missing property "project.build.outputTimestamp"
[
https://issues.apache.org/jira/browse/MPOM-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404231#comment-17404231
]
Herve Boutemy edited comment on MPOM-266 at 8/25/21, 7:06 AM:
--
notice that given we'll probably remove that check in MPOM-265 given the check
does not support parent POM projects, the message will disappear...
but probably such explanation would remain useful in
https://maven.apache.org/guides/mini/guide-reproducible-builds.html
(even if people won't read complex documentation: at least intro can remain
simple, hiding that subtle case, and FAQ part can provide details for motivated
people)
was (Author: hboutemy):
notice that given we'll probably remove that check in MPOM-265 given the check
does not support parent POM projects, the message will disappear...
> Incorrect message with missing property "project.build.outputTimestamp"
> ---
>
> Key: MPOM-266
> URL: https://issues.apache.org/jira/browse/MPOM-266
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-24
>Reporter: Konrad Windszus
>Priority: Major
>
> The check introduced with MPOM-255 emits the following error message:
> bq. The property "project.build.outputTimestamp" must be set on the reactor's
> root pom.xml to make the build reproducible. Further information at
> "https://maven.apache.org/guides/mini/guide-reproducible-builds.html";.
> Having the property on the reactor's root pom.xml is not sufficient though in
> case reactor root != parent.
> Consider the following project structure
> {code}
> reactor root (has no parent)
> + module1 (has parent: parent)
> + parent (has parent: asf-parent)
> {code}
> In this case setting the property in {{reactor root}} is not enough, as each
> module's effective pom.xml must contain the property
> {{project.build.outputTimestamp}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MPOM-266) Incorrect message with missing property "project.build.outputTimestamp"
[
https://issues.apache.org/jira/browse/MPOM-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404231#comment-17404231
]
Herve Boutemy commented on MPOM-266:
notice that given we'll probably remove that check in MPOM-265 given the check
does not support parent POM projects, the message will disappear...
> Incorrect message with missing property "project.build.outputTimestamp"
> ---
>
> Key: MPOM-266
> URL: https://issues.apache.org/jira/browse/MPOM-266
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-24
>Reporter: Konrad Windszus
>Priority: Major
>
> The check introduced with MPOM-255 emits the following error message:
> bq. The property "project.build.outputTimestamp" must be set on the reactor's
> root pom.xml to make the build reproducible. Further information at
> "https://maven.apache.org/guides/mini/guide-reproducible-builds.html";.
> Having the property on the reactor's root pom.xml is not sufficient though in
> case reactor root != parent.
> Consider the following project structure
> {code}
> reactor root (has no parent)
> + module1 (has parent: parent)
> + parent (has parent: asf-parent)
> {code}
> In this case setting the property in {{reactor root}} is not enough, as each
> module's effective pom.xml must contain the property
> {{project.build.outputTimestamp}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
