[jira] [Commented] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn
[
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544164#comment-17544164
]
Konrad Windszus commented on MRELEASE-1072:
---
There is no limitation around using the scm tag element mentioned anywhere
(neither in https://maven.apache.org/pom.html#SCM nor anywhere in
https://maven.apache.org/maven-release/maven-release-plugin/index.html) and it
is helpful for purposes when using both SVN and a GitHub mirror in the SCM
section. In any case just clearing it after the release is unexpected, so
release should either
1. try to keep (reset) the tag or
2. fail with an explicit error
> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element
> (e.g. with value "trunk") this is removed during prepare for the next
> snapshot version. The tagged/release version contains the properly adjusted
> tag element.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (DOXIASITETOOLS-254) Clarify inconsistencies in site decoration model
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated DOXIASITETOOLS-254:
-
Description:
[https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html]
bannerLeft/bannerRight:
* Are {{name}} and {{src}} (image) mutually exclusive? If yes, in what order
should they appear? Why is no {{position}} like with other similar elements
(logo, item)?
* Does {{href}} truly only apply to the image?
* Why is there no {{target}}?
* Must {{title}}/{{alt}} only be used on the image?
* Why not apply here the same logic as with the other imaged elements?
* Why {{src}} instead of {{img}} like the rest?
logo/link item/menu/menu item:
* Does {{href}} truly only to the text? (different to banner)
* Must {{title}}/{{alt}} only be used on the image?
was:
[https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html]
bannerLeft/bannerRight:
* Are {{name}} and {{src}} (image) mutually exclusive? If yes, in what order
should they appear? Why is no {{position}} like with other similar elements?
* Does {{href}} truly only apply to the image?
* Why is there no {{{}target{}}}?
* Must {{{}title{}}}/{{{}alt{}}} only be used on the image?
* Why not apply here the same logic as with the other imaged elements?
* Why {{src}} instead of {{img}} like the rest?
logo/link item/menu/menu itelm:
* Does {{href}} truly only to the text? (different to banner)
* Must {{{}title{}}}/{{{}alt{}}} only be used on the image?
> Clarify inconsistencies in site decoration model
>
>
> Key: DOXIASITETOOLS-254
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-254
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Decoration model
>Affects Versions: 1.11.1
>Reporter: Michael Osipov
>Priority: Major
>
> [https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html]
> bannerLeft/bannerRight:
> * Are {{name}} and {{src}} (image) mutually exclusive? If yes, in what order
> should they appear? Why is no {{position}} like with other similar elements
> (logo, item)?
> * Does {{href}} truly only apply to the image?
> * Why is there no {{target}}?
> * Must {{title}}/{{alt}} only be used on the image?
> * Why not apply here the same logic as with the other imaged elements?
> * Why {{src}} instead of {{img}} like the rest?
> logo/link item/menu/menu item:
> * Does {{href}} truly only to the text? (different to banner)
> * Must {{title}}/{{alt}} only be used on the image?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-enforcer] slawekjaranowski merged pull request #152: [MENFORCER-420] cache dependencies across rules
slawekjaranowski merged PR #152: URL: https://github.com/apache/maven-enforcer/pull/152 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MENFORCER-420) Reuse getDependenciesToCheck results across rules
[
https://issues.apache.org/jira/browse/MENFORCER-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed MENFORCER-420.
-
Assignee: Slawomir Jaranowski
Resolution: Fixed
> Reuse getDependenciesToCheck results across rules
> -
>
> Key: MENFORCER-420
> URL: https://issues.apache.org/jira/browse/MENFORCER-420
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
>Reporter: Joseph Walton
>Assignee: Slawomir Jaranowski
>Priority: Minor
> Fix For: 3.0.1
>
>
> We have a build with a significant number of dependencies, and also a large
> number of {{}} rules. Together, they lead to a build
> where Enforcer takes tens of minutes.
> Looking into bottlenecks, we found that
> {{AbstractBanDependencies#getDependenciesToCheck}} was taking a significant
> proportion of the build time (tens of percent). This method is called once
> per rule, so it's recalculating the dependencies for every rule across every
> execution.
> Introducing a cache, to reuse the dependencies one they'd been calculated for
> a module, dropped the time spent in banned dependency enforcement by about
> 75%, which was reflected as a 60% improvement in the time of that build.
> Our local implementation used the {{org.codehaus.plexus.context.Context}} to
> store the dependencies keyed by the concatenation of {{MavenProject#getId}}
> and {{searchTransitive}}; there may be a more appropriate scope to avoid edge
> cases with complex configurations.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MENFORCER-420) Reuse getDependenciesToCheck results across rules
[
https://issues.apache.org/jira/browse/MENFORCER-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544182#comment-17544182
]
Hudson commented on MENFORCER-420:
--
Build failed in Jenkins: Maven » Maven TLP » maven-enforcer » master #26
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/26/
> Reuse getDependenciesToCheck results across rules
> -
>
> Key: MENFORCER-420
> URL: https://issues.apache.org/jira/browse/MENFORCER-420
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
>Reporter: Joseph Walton
>Assignee: Slawomir Jaranowski
>Priority: Minor
> Fix For: 3.0.1
>
>
> We have a build with a significant number of dependencies, and also a large
> number of {{}} rules. Together, they lead to a build
> where Enforcer takes tens of minutes.
> Looking into bottlenecks, we found that
> {{AbstractBanDependencies#getDependenciesToCheck}} was taking a significant
> proportion of the build time (tens of percent). This method is called once
> per rule, so it's recalculating the dependencies for every rule across every
> execution.
> Introducing a cache, to reuse the dependencies one they'd been calculated for
> a module, dropped the time spent in banned dependency enforcement by about
> 75%, which was reflected as a 60% improvement in the time of that build.
> Our local implementation used the {{org.codehaus.plexus.context.Context}} to
> store the dependencies keyed by the concatenation of {{MavenProject#getId}}
> and {{searchTransitive}}; there may be a more appropriate scope to avoid edge
> cases with complex configurations.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (DOXIASITETOOLS-254) Clarify inconsistencies in site decoration model
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIASITETOOLS-254:
--
Description:
[https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html]
bannerLeft/bannerRight:
* Are {{name}} and {{src}} (image) mutually exclusive? If yes, in what order
should they appear? Why is no {{position}} like with other similar elements
(logo, item)?
* Does {{href}} truly only apply to the image?
* Why is there no {{target}}?
* Must {{title}}/{{alt}} only be used on the image?
* Why not apply here the same logic as with the other imaged elements?
* Why {{src}} instead of {{img}} like the rest?
logo/link item/menu/menu item:
* Does {{href}} truly only apply to the text? (different to banner)
* Must {{title}}/{{alt}} only be used on the image?
was:
[https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html]
bannerLeft/bannerRight:
* Are {{name}} and {{src}} (image) mutually exclusive? If yes, in what order
should they appear? Why is no {{position}} like with other similar elements
(logo, item)?
* Does {{href}} truly only apply to the image?
* Why is there no {{target}}?
* Must {{title}}/{{alt}} only be used on the image?
* Why not apply here the same logic as with the other imaged elements?
* Why {{src}} instead of {{img}} like the rest?
logo/link item/menu/menu item:
* Does {{href}} truly only to the text? (different to banner)
* Must {{title}}/{{alt}} only be used on the image?
> Clarify inconsistencies in site decoration model
>
>
> Key: DOXIASITETOOLS-254
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-254
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Decoration model
>Affects Versions: 1.11.1
>Reporter: Michael Osipov
>Priority: Major
>
> [https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html]
> bannerLeft/bannerRight:
> * Are {{name}} and {{src}} (image) mutually exclusive? If yes, in what order
> should they appear? Why is no {{position}} like with other similar elements
> (logo, item)?
> * Does {{href}} truly only apply to the image?
> * Why is there no {{target}}?
> * Must {{title}}/{{alt}} only be used on the image?
> * Why not apply here the same logic as with the other imaged elements?
> * Why {{src}} instead of {{img}} like the rest?
> logo/link item/menu/menu item:
> * Does {{href}} truly only apply to the text? (different to banner)
> * Must {{title}}/{{alt}} only be used on the image?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-surefire] sman-81 commented on pull request #535: [SUREFIRE-2086] Management of temporary files
sman-81 commented on PR #535: URL: https://github.com/apache/maven-surefire/pull/535#issuecomment-1141822955 hi @michael-o I've answered to the requested changes. Anything else that needs to be done before accepting this pull request? -- 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-release] nielsbasjes commented on a diff in pull request #132: [MRELEASE-1096] Many cleanups and updates
nielsbasjes commented on code in PR #132:
URL: https://github.com/apache/maven-release/pull/132#discussion_r885352045
##
maven-release-manager/pom.xml:
##
@@ -284,7 +284,7 @@
org.codehaus.plexus
plexus-maven-plugin
-1.3.8
+${plexus-maven-plugin.version}
Review Comment:
That commit you mentioned seems to be committed.
Yet I still see this plugin in the master branch
https://github.com/apache/maven-release/blob/master/maven-release-manager/pom.xml#L284
What do you want me to change in this pull request?
--
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-release] nielsbasjes commented on a diff in pull request #132: [MRELEASE-1096] Many cleanups and updates
nielsbasjes commented on code in PR #132:
URL: https://github.com/apache/maven-release/pull/132#discussion_r885354347
##
maven-release-manager/pom.xml:
##
@@ -284,7 +284,7 @@
org.codehaus.plexus
plexus-maven-plugin
-1.3.8
+${plexus-maven-plugin.version}
Review Comment:
I double checked and this specific code fragment was not removed as part of
#118
Do you want me to remove it as part of this pull request?
--
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] (MINDEXER-156) upgrade maven-bundle-plugin, fixes OSGi reproducibility issue
[ https://issues.apache.org/jira/browse/MINDEXER-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated MINDEXER-156: - Fix Version/s: 6.2.1 (was: next) > upgrade maven-bundle-plugin, fixes OSGi reproducibility issue > - > > Key: MINDEXER-156 > URL: https://issues.apache.org/jira/browse/MINDEXER-156 > Project: Maven Indexer > Issue Type: Dependency upgrade >Affects Versions: 6.2.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 6.2.1 > > > see > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/indexer/maven-indexer-6.2.0.diffoscope -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-doxia] dependabot[bot] opened a new pull request, #103: Bump flexmark-all from 0.50.50 to 0.64.0
dependabot[bot] opened a new pull request, #103: URL: https://github.com/apache/maven-doxia/pull/103 Bumps [flexmark-all](https://github.com/vsch/flexmark-java) from 0.50.50 to 0.64.0. Commits https://github.com/vsch/flexmark-java/commit/7c187fb2bcf3bbdad4a75226a746aee752255675";>7c187fb release 0.64.0 https://github.com/vsch/flexmark-java/commit/365843902e3deac30be3fc87a8d895aa61aac46a";>3658439 fix rename xml namespace constants https://github.com/vsch/flexmark-java/commit/cc669b238a467bdc790fdc4574169aae1e78420c";>cc669b2 fix namespace regex for efficiency https://github.com/vsch/flexmark-java/commit/5d8ccbcfc7c31c00d8f5ca08b80d0dc43e5152b6";>5d8ccbc add allow namespace to HTML parser. https://github.com/vsch/flexmark-java/commit/2b0cadfe32898e8aebe4745f4cef4b12ba14fc8c";>2b0cadf Merge remote-tracking branch 'origin/master' https://github.com/vsch/flexmark-java/commit/7ade901d9e7dbd0357156898cedb0742834bc450";>7ade901 add flexmark-ext-resizable-image (https://github-redirect.dependabot.com/vsch/flexmark-java/issues/489";>#489) https://github.com/vsch/flexmark-java/commit/1bce503c5755f2e6e8b99dc490a57c16ebc223ae";>1bce503 Merge remote-tracking branch 'origin/master' https://github.com/vsch/flexmark-java/commit/3eccbef6d8e0e790fd4a30ad01dd72fa4ca8c577";>3eccbef Fix for https://github-redirect.dependabot.com/vsch/flexmark-java/issues/435";>vsch/flexmark-java#435 (https://github-redirect.dependabot.com/vsch/flexmark-java/issues/480";>#480) https://github.com/vsch/flexmark-java/commit/dbd1c14b533418d22a6037c101340baef49208cf";>dbd1c14 Merge remote-tracking branch 'origin/master' https://github.com/vsch/flexmark-java/commit/f7721029d9f88d5dd818ef63f5960e7b73ee4855";>f772102 Fix issue with Jira conversion of mixed lists, including test case. (https://github-redirect.dependabot.com/vsch/flexmark-java/issues/453";>#453) Additional commits viewable in https://github.com/vsch/flexmark-java/compare/0.50.50...0.64.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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] (MINDEXER-158) IndexSearcher doesn't return all sha1
[
https://issues.apache.org/jira/browse/MINDEXER-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544404#comment-17544404
]
Tamás Cservenák commented on MINDEXER-158:
--
For this use case (give me all) indexer-reader is better suited, as it
gives you "raw" index records using much simpler API.
The mentioned two SHA1 checksums are for JAR and module file, so it is possible
that module is replacing the jar on index (so is a bug), as it differs only by
extension. This is actually not even a maven layout in it's conventional
sense will need to look into it.
> IndexSearcher doesn't return all sha1
> -
>
> Key: MINDEXER-158
> URL: https://issues.apache.org/jira/browse/MINDEXER-158
> Project: Maven Indexer
> Issue Type: Bug
>Reporter: Matteo Di Pierro
>Priority: Major
> Attachments: mavensnippet.java
>
>
> I'm following your example
> [here|https://github.com/apache/maven-indexer/blob/master/indexer-examples/indexer-examples-basic/src/main/java/org/apache/maven/index/examples/BasicUsageExample.java]
> and I am successfully able to download and open the index. However, I cannot
> find the sha1 d62bd1ef6a9aee74557bd59fb96030fd52cf2fc1, while if I run
> {code:java}
> curl
> https://search.maven.org/solrsearch/select?q="1:d62bd1ef6a9aee74557bd59fb96030fd52cf2fc1"{code}
> I get
>
> {code:java}
> {"responseHeader":{"status":0,"QTime":0,"params":{"q":"1:d62bd1ef6a9aee74557bd59fb96030fd52cf2fc1","core":"","indent":"off","fl":"id,g,a,v,p,ec,timestamp,tags","start":"","sort":"score
> desc,timestamp desc,g asc,a asc,v
> desc","rows":"20","wt":"json","version":"2.2"}},"response":{"numFound":1,"start":0,"docs":[{"id":"org.springframework:spring-webmvc:5.3.17","g":"org.springframework","a":"spring-webmvc","v":"5.3.17","p":"jar","timestamp":1647516151000,"ec":[".module","-sources.jar",".pom","-javadoc.jar",".jar"],"tags":["spring"]}]}}
> {code}
>
>
> I am instead able to find inside the index the sha1
> 3f4de0db59b9085e41cc11c8c2914c427cc848e1 related to the same pkg, as shown
> here:
> {code:java}
> curl
> https://search.maven.org/solrsearch/select?q="1:3f4de0db59b9085e41cc11c8c2914c427cc848e1";
> {"responseHeader":{"status":0,"QTime":0,"params":{"q":"1:3f4de0db59b9085e41cc11c8c2914c427cc848e1","core":"","indent":"off","fl":"id,g,a,v,p,ec,timestamp,tags","start":"","sort":"score
> desc,timestamp desc,g asc,a asc,v
> desc","rows":"20","wt":"json","version":"2.2"}},"response":{"numFound":1,"start":0,"docs":[{"id":"org.springframework:spring-webmvc:5.3.17","g":"org.springframework","a":"spring-webmvc","v":"5.3.17","p":"jar","timestamp":1647516151000,"ec":[".module","-sources.jar",".pom","-javadoc.jar",".jar"],"tags":["spring"]}]}}{code}
> Can you please help me to retrieve all the sha1 from the index?
> I attach here the code I'm using [^mavensnippet.java].
> Thank you very much
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (MINDEXER-158) IndexSearcher doesn't return all sha1
[
https://issues.apache.org/jira/browse/MINDEXER-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák reassigned MINDEXER-158:
Assignee: Tamás Cservenák
> IndexSearcher doesn't return all sha1
> -
>
> Key: MINDEXER-158
> URL: https://issues.apache.org/jira/browse/MINDEXER-158
> Project: Maven Indexer
> Issue Type: Bug
>Reporter: Matteo Di Pierro
>Assignee: Tamás Cservenák
>Priority: Major
> Attachments: mavensnippet.java
>
>
> I'm following your example
> [here|https://github.com/apache/maven-indexer/blob/master/indexer-examples/indexer-examples-basic/src/main/java/org/apache/maven/index/examples/BasicUsageExample.java]
> and I am successfully able to download and open the index. However, I cannot
> find the sha1 d62bd1ef6a9aee74557bd59fb96030fd52cf2fc1, while if I run
> {code:java}
> curl
> https://search.maven.org/solrsearch/select?q="1:d62bd1ef6a9aee74557bd59fb96030fd52cf2fc1"{code}
> I get
>
> {code:java}
> {"responseHeader":{"status":0,"QTime":0,"params":{"q":"1:d62bd1ef6a9aee74557bd59fb96030fd52cf2fc1","core":"","indent":"off","fl":"id,g,a,v,p,ec,timestamp,tags","start":"","sort":"score
> desc,timestamp desc,g asc,a asc,v
> desc","rows":"20","wt":"json","version":"2.2"}},"response":{"numFound":1,"start":0,"docs":[{"id":"org.springframework:spring-webmvc:5.3.17","g":"org.springframework","a":"spring-webmvc","v":"5.3.17","p":"jar","timestamp":1647516151000,"ec":[".module","-sources.jar",".pom","-javadoc.jar",".jar"],"tags":["spring"]}]}}
> {code}
>
>
> I am instead able to find inside the index the sha1
> 3f4de0db59b9085e41cc11c8c2914c427cc848e1 related to the same pkg, as shown
> here:
> {code:java}
> curl
> https://search.maven.org/solrsearch/select?q="1:3f4de0db59b9085e41cc11c8c2914c427cc848e1";
> {"responseHeader":{"status":0,"QTime":0,"params":{"q":"1:3f4de0db59b9085e41cc11c8c2914c427cc848e1","core":"","indent":"off","fl":"id,g,a,v,p,ec,timestamp,tags","start":"","sort":"score
> desc,timestamp desc,g asc,a asc,v
> desc","rows":"20","wt":"json","version":"2.2"}},"response":{"numFound":1,"start":0,"docs":[{"id":"org.springframework:spring-webmvc:5.3.17","g":"org.springframework","a":"spring-webmvc","v":"5.3.17","p":"jar","timestamp":1647516151000,"ec":[".module","-sources.jar",".pom","-javadoc.jar",".jar"],"tags":["spring"]}]}}{code}
> Can you please help me to retrieve all the sha1 from the index?
> I attach here the code I'm using [^mavensnippet.java].
> Thank you very much
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-plugin-tools] dependabot[bot] opened a new pull request, #94: Bump assertj-core from 3.22.0 to 3.23.0
dependabot[bot] opened a new pull request, #94: URL: https://github.com/apache/maven-plugin-tools/pull/94 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.22.0 to 3.23.0. Commits https://github.com/assertj/assertj-core/commit/6f19754e579527b935c9e62d5cb5b0900fa1e6a1";>6f19754 [maven-release-plugin] prepare release assertj-core-3.23.0 https://github.com/assertj/assertj-core/commit/c592c18a59a1ef4f681f1eb08b2571fa77757e43";>c592c18 Expose ComparisonStrategy::areEqual in AbstractAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2633";>#2633) https://github.com/assertj/assertj-core/commit/69c66a9bb66f8b8a39535eb769e8c97d0d8c6648";>69c66a9 Bump maven-invoker-plugin from 3.2.2 to 3.3.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2636";>#2636) https://github.com/assertj/assertj-core/commit/795f5278bebb2703eda7b11569403c2bed650d5a";>795f527 Fix test https://github.com/assertj/assertj-core/commit/b44460623b9c0e83c2b311c1fc6b7bffa1a077b9";>b444606 Bump hibernate-core from 6.0.1.Final to 6.0.2.Final (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2626";>#2626) https://github.com/assertj/assertj-core/commit/793241125ee85ac832a6ee12fc77456256c5";>7932411 Fix typos in Javadoc of ObjectEnumerableAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2624";>#2624) https://github.com/assertj/assertj-core/commit/b746e6aeb4b9bd7246797c3fc18059977aac6ab3";>b746e6a [mvn] Update maven wrapper to 3.1.1 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2622";>#2622) https://github.com/assertj/assertj-core/commit/59e27a0aa603705032c9ef2e764113991a79d10b";>59e27a0 Add linesOf variants for a Path content (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2618";>#2618) https://github.com/assertj/assertj-core/commit/24c4fcb4f1d67dd5b51e085951f5702f87e12170";>24c4fcb Add binary compatibility result to job summary https://github.com/assertj/assertj-core/commit/b23f797b88253ed6cfcc7ddf17504480d5340e6e";>b23f797 Bump cdg.pitest.version from 0.1.3 to 0.2.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2619";>#2619) Additional commits viewable in https://github.com/assertj/assertj-core/compare/assertj-core-3.22.0...assertj-core-3.23.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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] (SCM-990) Jgit Provider cannot resolve Repository in multi-module Maven Project
Enrico Horn created SCM-990: --- Summary: Jgit Provider cannot resolve Repository in multi-module Maven Project Key: SCM-990 URL: https://issues.apache.org/jira/browse/SCM-990 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-jgit Reporter: Enrico Horn The JGit providers info command (and probably others) uses fielset.basedir as git working directory. When running maven command in a submodule this will result in the following error: Cannot get the revision information from the scm repository : [ERROR] Exception while executing SCM command. JGit resolve failure! repository not found: What it should do instead is act like the git binary and search for the git directory in parent directories if none found in the current one. Jgit has the API FileRepositoryBuilder.findGitDir to do that. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (SCM-990) Jgit Provider cannot resolve Repository in multi-module Maven Project
[
https://issues.apache.org/jira/browse/SCM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1751#comment-1751
]
Michael Osipov commented on SCM-990:
That is not a bug. You must invoke from the parent and use {{-pl}}.
> Jgit Provider cannot resolve Repository in multi-module Maven Project
> -
>
> Key: SCM-990
> URL: https://issues.apache.org/jira/browse/SCM-990
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-jgit
>Reporter: Enrico Horn
>Priority: Major
>
> The JGit providers info command (and probably others) uses fielset.basedir as
> git working directory. When running maven command in a submodule this will
> result in the following error:
>
> Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. JGit resolve failure!
> repository not found:
>
> What it should do instead is act like the git binary and search for the git
> directory in parent directories if none found in the current one. Jgit has
> the API FileRepositoryBuilder.findGitDir to do that.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MRELEASE-1091) Use non-interactive (batch) mode for forked Maven process
[ https://issues.apache.org/jira/browse/MRELEASE-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRELEASE-1091: - Summary: Use non-interactive (batch) mode for forked Maven process (was: Use non-interactive(batch) mode for forked Maven process) > Use non-interactive (batch) mode for forked Maven process > - > > Key: MRELEASE-1091 > URL: https://issues.apache.org/jira/browse/MRELEASE-1091 > Project: Maven Release Plugin > Issue Type: Bug >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.0.0-M6 > > > Due to bug MSHARED-1072 we can't use interactive mode for forked Maven > process. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-release] michael-o commented on a diff in pull request #132: [MRELEASE-1096] Many cleanups and updates
michael-o commented on code in PR #132:
URL: https://github.com/apache/maven-release/pull/132#discussion_r885766335
##
maven-release-manager/pom.xml:
##
@@ -284,7 +284,7 @@
org.codehaus.plexus
plexus-maven-plugin
-1.3.8
+${plexus-maven-plugin.version}
Review Comment:
Drop it
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-enforcer] dependabot[bot] opened a new pull request, #158: Bump assertj-core from 3.22.0 to 3.23.0
dependabot[bot] opened a new pull request, #158: URL: https://github.com/apache/maven-enforcer/pull/158 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.22.0 to 3.23.0. Commits https://github.com/assertj/assertj-core/commit/6f19754e579527b935c9e62d5cb5b0900fa1e6a1";>6f19754 [maven-release-plugin] prepare release assertj-core-3.23.0 https://github.com/assertj/assertj-core/commit/c592c18a59a1ef4f681f1eb08b2571fa77757e43";>c592c18 Expose ComparisonStrategy::areEqual in AbstractAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2633";>#2633) https://github.com/assertj/assertj-core/commit/69c66a9bb66f8b8a39535eb769e8c97d0d8c6648";>69c66a9 Bump maven-invoker-plugin from 3.2.2 to 3.3.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2636";>#2636) https://github.com/assertj/assertj-core/commit/795f5278bebb2703eda7b11569403c2bed650d5a";>795f527 Fix test https://github.com/assertj/assertj-core/commit/b44460623b9c0e83c2b311c1fc6b7bffa1a077b9";>b444606 Bump hibernate-core from 6.0.1.Final to 6.0.2.Final (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2626";>#2626) https://github.com/assertj/assertj-core/commit/793241125ee85ac832a6ee12fc77456256c5";>7932411 Fix typos in Javadoc of ObjectEnumerableAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2624";>#2624) https://github.com/assertj/assertj-core/commit/b746e6aeb4b9bd7246797c3fc18059977aac6ab3";>b746e6a [mvn] Update maven wrapper to 3.1.1 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2622";>#2622) https://github.com/assertj/assertj-core/commit/59e27a0aa603705032c9ef2e764113991a79d10b";>59e27a0 Add linesOf variants for a Path content (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2618";>#2618) https://github.com/assertj/assertj-core/commit/24c4fcb4f1d67dd5b51e085951f5702f87e12170";>24c4fcb Add binary compatibility result to job summary https://github.com/assertj/assertj-core/commit/b23f797b88253ed6cfcc7ddf17504480d5340e6e";>b23f797 Bump cdg.pitest.version from 0.1.3 to 0.2.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2619";>#2619) Additional commits viewable in https://github.com/assertj/assertj-core/compare/assertj-core-3.22.0...assertj-core-3.23.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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] (SCM-990) Jgit Provider cannot resolve Repository in multi-module Maven Project
[ https://issues.apache.org/jira/browse/SCM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544455#comment-17544455 ] Enrico Horn commented on SCM-990: - # This works with the default scm provider which is probably gitexe # Maven allows this behaviopur in a multi module project. Yes, this is a bug. > Jgit Provider cannot resolve Repository in multi-module Maven Project > - > > Key: SCM-990 > URL: https://issues.apache.org/jira/browse/SCM-990 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-jgit >Reporter: Enrico Horn >Priority: Major > > The JGit providers info command (and probably others) uses fielset.basedir as > git working directory. When running maven command in a submodule this will > result in the following error: > > Cannot get the revision information from the scm repository : > [ERROR] Exception while executing SCM command. JGit resolve failure! > repository not found: > > What it should do instead is act like the git binary and search for the git > directory in parent directories if none found in the current one. Jgit has > the API FileRepositoryBuilder.findGitDir to do that. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-release] nielsbasjes commented on a diff in pull request #132: [MRELEASE-1096] Many cleanups and updates
nielsbasjes commented on code in PR #132:
URL: https://github.com/apache/maven-release/pull/132#discussion_r885797909
##
maven-release-manager/pom.xml:
##
@@ -284,7 +284,7 @@
org.codehaus.plexus
plexus-maven-plugin
-1.3.8
+${plexus-maven-plugin.version}
Review Comment:
aaand it's gone
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Closed] (SUREFIRE-2061) BLOCKED in surefire-forkedjvm-stream-flusher
[
https://issues.apache.org/jira/browse/SUREFIRE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed SUREFIRE-2061.
-
Resolution: Fixed
> BLOCKED in surefire-forkedjvm-stream-flusher
>
>
> Key: SUREFIRE-2061
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2061
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Slawomir Jaranowski
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M7
>
>
> From time to time test execution is hung up - wait forever ...
> Now I can't reproduce it, test rerun fix it.
> The stack is:
> {code}
> 2022-04-06 13:59:05
> Full thread dump OpenJDK 64-Bit Server VM (25.322-b00 mixed mode):
> "Attach Listener" #16 daemon prio=9 os_prio=31 tid=0x7fe48036a000
> nid=0x380b waiting on condition [0x]
>java.lang.Thread.State: RUNNABLE
> "surefire-forkedjvm-command-thread" #12 daemon prio=5 os_prio=31
> tid=0x7fe504a5c000 nid=0xa803 runnable [0x7db43000]
>java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> - locked <0x0005c000ccb0> (a java.io.BufferedInputStream)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> - locked <0x0005c000ccd8> (a java.io.BufferedInputStream)
> at
> org.apache.maven.surefire.api.util.internal.Channels$3.readImpl(Channels.java:217)
> at
> org.apache.maven.surefire.api.util.internal.AbstractNoninterruptibleReadableChannel.read(AbstractNoninterruptibleReadableChannel.java:54)
> at
> org.apache.maven.surefire.api.stream.AbstractStreamDecoder.read(AbstractStreamDecoder.java:487)
> at
> org.apache.maven.surefire.api.stream.AbstractStreamDecoder.read(AbstractStreamDecoder.java:473)
> at
> org.apache.maven.surefire.api.stream.AbstractStreamDecoder.readMessageType(AbstractStreamDecoder.java:118)
> at
> org.apache.maven.surefire.booter.stream.CommandDecoder.decode(CommandDecoder.java:87)
> at
> org.apache.maven.surefire.booter.spi.CommandChannelDecoder.decode(CommandChannelDecoder.java:67)
> at
> org.apache.maven.surefire.booter.CommandReader$CommandRunnable.run(CommandReader.java:345)
> at java.lang.Thread.run(Thread.java:750)
> "surefire-forkedjvm-stream-flusher" #10 daemon prio=5 os_prio=31
> tid=0x7fe500969000 nid=0xa903 waiting for monitor entry
> [0x7da4]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at java.io.BufferedOutputStream.write(BufferedOutputStream.java:117)
> - waiting to lock <0x0005c000d498> (a java.io.BufferedOutputStream)
> at
> org.apache.maven.surefire.api.util.internal.Channels$4.writeImpl(Channels.java:253)
> at
> org.apache.maven.surefire.api.util.internal.AbstractNoninterruptibleWritableChannel.write(AbstractNoninterruptibleWritableChannel.java:72)
> at
> org.apache.maven.surefire.api.util.internal.AbstractNoninterruptibleWritableChannel.write(AbstractNoninterruptibleWritableChannel.java:45)
> at
> org.apache.maven.surefire.booter.spi.AbstractMasterProcessChannelProcessorFactory$1.run(AbstractMasterProcessChannelProcessorFactory.java:65)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:750)
> "Service Thread" #9 daemon prio=9 os_prio=31 tid=0x7fe50003a800
> nid=0x5603 runnable [0x]
>java.lang.Thread.State: RUNNABLE
> "C1 CompilerThread3" #8 daemon prio=9 os_prio=31 tid=0x7fe50001f800
> nid=0x3f03 waiting on condition [0x]
>java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread2" #7 daemon prio=9 os_prio=31 tid=0x7fe5e800
> nid=0x4103 waiting on condition [0x]
>java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread1" #6 daemon prio=9 os_prio=31 tid=0x7fe4f607e800
> ni
[GitHub] [maven-mvnd] digulla commented on issue #619: Problem when running in Cygwin with an existed env variable “JAVA_HOME”.
digulla commented on issue #619:
URL: https://github.com/apache/maven-mvnd/issues/619#issuecomment-1142317006
My suggestion would be to check whether `cygpath` is on the PATH or detect
cygwin using `uname -s`. If a path doesn't work, try to run it through `cygpath
--windows ` and try again.
Something like using this everywhere:
File path = resolveLocalPath(...)
and then having code like this in resolveLocalPath():
if file.exists() return file;
if (cygwin) { // cygwin
String mightWork = runOSCommand("cygpath", "--windows",
file.toString());
File f = new File(mightWork);
if (f.exists()) { return file)
}
`uname -s` returns `CYGWIN_NT-10.0-19042`. I suggest to check for
`String.startsWith("CYGWIN")`
--
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-mvnd] digulla commented on issue #619: Problem when running in Cygwin with an existed env variable “JAVA_HOME”.
digulla commented on issue #619: URL: https://github.com/apache/maven-mvnd/issues/619#issuecomment-1142322717 Workaround: Run this command to set JAVA_HOME in such a way that mvnd can use it: export JAVA_HOME="$(cygpath --windows ~/.sdkman/candidates/java/current)" -- 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] (SCM-990) Jgit Provider cannot resolve Repository in multi-module Maven Project
[ https://issues.apache.org/jira/browse/SCM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544481#comment-17544481 ] Michael Osipov commented on SCM-990: A multimodule build is supposed to be run from the root/parent. If you want to run a single module, still run from root/parent and projects option. Did you try it at least? > Jgit Provider cannot resolve Repository in multi-module Maven Project > - > > Key: SCM-990 > URL: https://issues.apache.org/jira/browse/SCM-990 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-jgit >Reporter: Enrico Horn >Priority: Major > > The JGit providers info command (and probably others) uses fielset.basedir as > git working directory. When running maven command in a submodule this will > result in the following error: > > Cannot get the revision information from the scm repository : > [ERROR] Exception while executing SCM command. JGit resolve failure! > repository not found: > > What it should do instead is act like the git binary and search for the git > directory in parent directories if none found in the current one. Jgit has > the API FileRepositoryBuilder.findGitDir to do that. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (MJAVADOC-716) The stale file detection does not work
Guillaume Nodet created MJAVADOC-716:
Summary: The stale file detection does not work
Key: MJAVADOC-716
URL: https://issues.apache.org/jira/browse/MJAVADOC-716
Project: Maven Javadoc Plugin
Issue Type: Bug
Reporter: Guillaume Nodet
I always end up with {{Configuration changed, re-generating javadoc.}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MRELEASE-1098) Drop o.a.m.shared.release.env.ReleaseEnvironment.getLocale()
[ https://issues.apache.org/jira/browse/MRELEASE-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRELEASE-1098: - Description: No bundles are translated, all our code is English, nothing else. Other messages aren't even externalized. It makes no sense to provide an unused/unusable option. See also: https://github.com/apache/maven-release/pull/135#discussion_r884282247 (was: No bundles are translated, all our code is English, nothing else. Other messages aren't even externalized. It makes not sense to provide an unused option. See also: https://github.com/apache/maven-release/pull/135#discussion_r884282247) > Drop o.a.m.shared.release.env.ReleaseEnvironment.getLocale() > > > Key: MRELEASE-1098 > URL: https://issues.apache.org/jira/browse/MRELEASE-1098 > Project: Maven Release Plugin > Issue Type: Task >Affects Versions: 3.0.0-M5 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0-M6 > > > No bundles are translated, all our code is English, nothing else. Other > messages aren't even externalized. It makes no sense to provide an > unused/unusable option. See also: > https://github.com/apache/maven-release/pull/135#discussion_r884282247 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-pmd-plugin] adangel merged pull request #71: [MPMD-343] - Upgrade to PMD 6.46.0
adangel merged PR #71: URL: https://github.com/apache/maven-pmd-plugin/pull/71 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] dependabot[bot] commented on pull request #52: Bump commons-io from 2.6 to 2.11.0
dependabot[bot] commented on PR #52: URL: https://github.com/apache/maven-pmd-plugin/pull/52#issuecomment-1142385715 Looks like commons-io:commons-io is up-to-date now, so this is no longer needed. -- 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-pmd-plugin] dependabot[bot] closed pull request #52: Bump commons-io from 2.6 to 2.11.0
dependabot[bot] closed pull request #52: Bump commons-io from 2.6 to 2.11.0 URL: https://github.com/apache/maven-pmd-plugin/pull/52 -- 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-pmd-plugin] dependabot[bot] opened a new pull request, #72: Bump commons-lang3 from 3.8.1 to 3.12.0
dependabot[bot] opened a new pull request, #72: URL: https://github.com/apache/maven-pmd-plugin/pull/72 Bumps commons-lang3 from 3.8.1 to 3.12.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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] (MPMD-343) Upgrade to PMD 6.46.0
[ https://issues.apache.org/jira/browse/MPMD-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544501#comment-17544501 ] Andreas Dangel commented on MPMD-343: - Updated to PMD 6.46.0: https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=027bf252a306a95b5ef2f42bd55430dfdd74ea0e > Upgrade to PMD 6.46.0 > - > > Key: MPMD-343 > URL: https://issues.apache.org/jira/browse/MPMD-343 > 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] [Closed] (MPMD-343) Upgrade to PMD 6.46.0
[ https://issues.apache.org/jira/browse/MPMD-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-343. --- Resolution: Fixed > Upgrade to PMD 6.46.0 > - > > Key: MPMD-343 > URL: https://issues.apache.org/jira/browse/MPMD-343 > 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] (MPMD-336) Replace deprecated calls to PMD
[ https://issues.apache.org/jira/browse/MPMD-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544503#comment-17544503 ] Andreas Dangel commented on MPMD-336: - https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=f26bec9283e0e0857f48deb8f2945bb807129407 > Replace deprecated calls to PMD > --- > > Key: MPMD-336 > URL: https://issues.apache.org/jira/browse/MPMD-336 > Project: Maven PMD Plugin > Issue Type: Task >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > * configuration.prependClasspath > * Use PmdAnalysis instead of PMD.processFiles > * Use Report.filterViolations instead of creating a new Report instance -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (MPMD-336) Replace deprecated calls to PMD
[ https://issues.apache.org/jira/browse/MPMD-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-336. --- Resolution: Fixed > Replace deprecated calls to PMD > --- > > Key: MPMD-336 > URL: https://issues.apache.org/jira/browse/MPMD-336 > Project: Maven PMD Plugin > Issue Type: Task >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > * configuration.prependClasspath > * Use PmdAnalysis instead of PMD.processFiles > * Use Report.filterViolations instead of creating a new Report instance -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MPMD-343) Upgrade to PMD 6.46.0
[ https://issues.apache.org/jira/browse/MPMD-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544508#comment-17544508 ] Hudson commented on MPMD-343: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pmd-plugin » master #32 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/32/ > Upgrade to PMD 6.46.0 > - > > Key: MPMD-343 > URL: https://issues.apache.org/jira/browse/MPMD-343 > 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] [Assigned] (MWRAPPER-64) IT test use early deployed artifacts
[
https://issues.apache.org/jira/browse/MWRAPPER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned MWRAPPER-64:
---
Assignee: Slawomir Jaranowski
> IT test use early deployed artifacts
>
>
> Key: MWRAPPER-64
> URL: https://issues.apache.org/jira/browse/MWRAPPER-64
> Project: Maven Wrapper
> Issue Type: Bug
>Affects Versions: 3.1.1
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Minor
>
> Test
> - type_script
> - type_source
> are using under test artifacts which was deployed in early build
> It is visible when we use project version which was not deployed anywhere,
> eg build from source-release.zip
> Default configuration of {{mrm plugin}} proxy everything using current Maven
> settings,
> so we have error:
> {code}
> Couldn't find .mvn/wrapper/maven-wrapper.jar, downloading it ...
> Downloading from:
> http://localhost:57805/org/apache/maven/wrapper/maven-wrapper/3.1.1/maven-wrapper-3.1.1.jar
> Found curl ... using curl
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
> 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
> curl: (22) The requested URL returned error: 404
> Error: Could not find or load main class
> org.apache.maven.wrapper.MavenWrapperMain
> [ERROR] Command execution failed.
> {code}
> We need configure {{mrm plugin}} to provide currently build artifacts.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-wrapper] slawekjaranowski opened a new pull request, #47: [MWRAPPER-64] Use currently build artifacts in IT tests
slawekjaranowski opened a new pull request, #47: URL: https://github.com/apache/maven-wrapper/pull/47 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MWRAPPER) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MWRAPPER-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MWRAPPER-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MWRAPPER-64) IT test use early deployed artifacts
[
https://issues.apache.org/jira/browse/MWRAPPER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544536#comment-17544536
]
ASF GitHub Bot commented on MWRAPPER-64:
slawekjaranowski opened a new pull request, #47:
URL: https://github.com/apache/maven-wrapper/pull/47
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MWRAPPER) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [x] Format the pull request title like `[MWRAPPER-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MWRAPPER-XXX` with the appropriate JIRA issue.
Best practice
is to use the JIRA issue title in the pull request title and in the
first line of the
commit message.
- [ ] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [x] You have run the integration tests successfully (`mvn -Prun-its clean
verify`).
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [x] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
> IT test use early deployed artifacts
>
>
> Key: MWRAPPER-64
> URL: https://issues.apache.org/jira/browse/MWRAPPER-64
> Project: Maven Wrapper
> Issue Type: Bug
>Affects Versions: 3.1.1
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Minor
>
> Test
> - type_script
> - type_source
> are using under test artifacts which was deployed in early build
> It is visible when we use project version which was not deployed anywhere,
> eg build from source-release.zip
> Default configuration of {{mrm plugin}} proxy everything using current Maven
> settings,
> so we have error:
> {code}
> Couldn't find .mvn/wrapper/maven-wrapper.jar, downloading it ...
> Downloading from:
> http://localhost:57805/org/apache/maven/wrapper/maven-wrapper/3.1.1/maven-wrapper-3.1.1.jar
> Found curl ... using curl
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
> 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
> curl: (22) The requested URL returned error: 404
> Error: Could not find or load main class
> org.apache.maven.wrapper.MavenWrapperMain
> [ERROR] Command execution failed.
> {code}
> We need configure {{mrm plugin}} to provide currently build artifacts.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-wrapper] slawekjaranowski merged pull request #45: [MWRAPPER] - Add doc for type flag
slawekjaranowski merged PR #45: URL: https://github.com/apache/maven-wrapper/pull/45 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-wrapper] slawekjaranowski commented on pull request #45: [MWRAPPER] - Add doc for type flag
slawekjaranowski commented on PR #45: URL: https://github.com/apache/maven-wrapper/pull/45#issuecomment-1142438015 @stonar96 thanks -- 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-enforcer] slawekjaranowski merged pull request #158: Bump assertj-core from 3.22.0 to 3.23.0
slawekjaranowski merged PR #158: URL: https://github.com/apache/maven-enforcer/pull/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
[jira] [Updated] (MENFORCER-356) Please support m2e lifecycle management
[ https://issues.apache.org/jira/browse/MENFORCER-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MENFORCER-356: -- Priority: Minor (was: Major) > Please support m2e lifecycle management > --- > > Key: MENFORCER-356 > URL: https://issues.apache.org/jira/browse/MENFORCER-356 > Project: Maven Enforcer Plugin > Issue Type: New Feature > Environment: Linux >Reporter: Luke Hutchison >Priority: Minor > Fix For: waiting-for-feedback > > > The maven-enforcer-plugin does not work with m2e without configuration using > the `lifecyleManagement` tag. However, that tag causes numerous bad > interactions between m2e and commandline mvn. > Recently m2e added a new configuration mechanism for specifying the lifecycle > management configuration: > [https://www.eclipse.org/m2e/documentation/release-notes-17.html#new-syntax-for-specifying-lifecycle-mapping-metadata] > The directive that works for me to get maven-enforcer-plugin to work with m2e > is: > > However, this style of directive, , breaks numerous tools, including > Sonatype's artifact publishing framework, and the Scrutinizer CI / static > code analyzer, because they use custom XML parsers that can't yet handle this > syntax. That means I have to leave the directive in the pom.xml while > developing, so that I can use Eclipse, and then I have to remove it before > publishing or analyzing any built jar. > It would be very helpful if maven-enforcer-plugin could make use of the m2e > lifecycle management API internally to configure itself to work with m2e, so > that this directive is not needed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MENFORCER-417) requireUpperBoundDeps doesn't work when dependencies are managed
[
https://issues.apache.org/jira/browse/MENFORCER-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544544#comment-17544544
]
Slawomir Jaranowski commented on MENFORCER-417:
---
Please retest with the latest snapshot version or provide simple project to
reproduce.
> requireUpperBoundDeps doesn't work when dependencies are managed
>
>
> Key: MENFORCER-417
> URL: https://issues.apache.org/jira/browse/MENFORCER-417
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
>Affects Versions: 3.0.0
>Reporter: James Howe
>Priority: Major
>
> {code:xml}
>
>
> {code}
> Example false-positive in a project using spring-boot-dependencies:
> {noformat}
> Failed while enforcing RequireUpperBoundDeps. The error(s) are [
> Require upper bound dependencies error for org.slf4j:slf4j-api:1.7.36 paths
> to dependency are:
> +-com.example:project:1.0-SNAPSHOT
>
> +-org.springframework.security.extensions:spring-security-saml2-core:1.0.10.RELEASE
> +-org.slf4j:slf4j-api:1.7.36 (managed) <-- org.slf4j:slf4j-api:1.7.29
> and
> +-com.example:project:1.0-SNAPSHOT
> +-com.github.zhanhb:thymeleaf-layout-dialect:3.0.0
> +-org.slf4j:slf4j-api:1.7.36 (managed) <-- org.slf4j:slf4j-api:1.7.32
> and
> +-com.example:project:1.0-SNAPSHOT
> +-org.springframework.boot:spring-boot-starter-logging:2.6.7 (managed) <--
> org.springframework.boot:spring-boot-starter-logging:2.6.7
> +-org.slf4j:jul-to-slf4j:1.7.36 (managed) <--
> org.slf4j:jul-to-slf4j:1.7.36
> +-org.slf4j:slf4j-api:1.7.36 (managed) <-- org.slf4j:slf4j-api:1.7.36
> ...
> {noformat}
> No version higher than 1.7.36 is listed anywhere, and at time of writing so
> such version has even been released (other than 2.0.0-alpha).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MENFORCER-417) requireUpperBoundDeps doesn't work when dependencies are managed
[
https://issues.apache.org/jira/browse/MENFORCER-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MENFORCER-417:
--
Fix Version/s: waiting-for-feedback
> requireUpperBoundDeps doesn't work when dependencies are managed
>
>
> Key: MENFORCER-417
> URL: https://issues.apache.org/jira/browse/MENFORCER-417
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
>Affects Versions: 3.0.0
>Reporter: James Howe
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> {code:xml}
>
>
> {code}
> Example false-positive in a project using spring-boot-dependencies:
> {noformat}
> Failed while enforcing RequireUpperBoundDeps. The error(s) are [
> Require upper bound dependencies error for org.slf4j:slf4j-api:1.7.36 paths
> to dependency are:
> +-com.example:project:1.0-SNAPSHOT
>
> +-org.springframework.security.extensions:spring-security-saml2-core:1.0.10.RELEASE
> +-org.slf4j:slf4j-api:1.7.36 (managed) <-- org.slf4j:slf4j-api:1.7.29
> and
> +-com.example:project:1.0-SNAPSHOT
> +-com.github.zhanhb:thymeleaf-layout-dialect:3.0.0
> +-org.slf4j:slf4j-api:1.7.36 (managed) <-- org.slf4j:slf4j-api:1.7.32
> and
> +-com.example:project:1.0-SNAPSHOT
> +-org.springframework.boot:spring-boot-starter-logging:2.6.7 (managed) <--
> org.springframework.boot:spring-boot-starter-logging:2.6.7
> +-org.slf4j:jul-to-slf4j:1.7.36 (managed) <--
> org.slf4j:jul-to-slf4j:1.7.36
> +-org.slf4j:slf4j-api:1.7.36 (managed) <-- org.slf4j:slf4j-api:1.7.36
> ...
> {noformat}
> No version higher than 1.7.36 is listed anywhere, and at time of writing so
> such version has even been released (other than 2.0.0-alpha).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (MENFORCER-421) Use currently build artifacts in IT tests
Slawomir Jaranowski created MENFORCER-421:
-
Summary: Use currently build artifacts in IT tests
Key: MENFORCER-421
URL: https://issues.apache.org/jira/browse/MENFORCER-421
Project: Maven Enforcer Plugin
Issue Type: Bug
Reporter: Slawomir Jaranowski
Assignee: Slawomir Jaranowski
Fix For: 3.0.1
Due to misconfigured of {{mrm-maven-plugin}} during IT test artifacts from
previous build are used or downloaded from remote repository
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MENFORCER-421) Use currently build artifacts in IT tests
[
https://issues.apache.org/jira/browse/MENFORCER-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MENFORCER-421:
--
Description:
Due to misconfigured of {{mrm-maven-plugin}} during IT test artifacts from
previous build are used or downloaded from remote repository.
{{localRepo}} of {{mrm-maven-plugin}} should be used with the same directory as
used for {{localRepositoryPath}} of maven-invoker-plugin
was:Due to misconfigured of {{mrm-maven-plugin}} during IT test artifacts
from previous build are used or downloaded from remote repository
> Use currently build artifacts in IT tests
> -
>
> Key: MENFORCER-421
> URL: https://issues.apache.org/jira/browse/MENFORCER-421
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.0.1
>
>
> Due to misconfigured of {{mrm-maven-plugin}} during IT test artifacts from
> previous build are used or downloaded from remote repository.
> {{localRepo}} of {{mrm-maven-plugin}} should be used with the same directory
> as used for {{localRepositoryPath}} of maven-invoker-plugin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-release] asfgit closed pull request #136: [MRELEASE-1098] Drop o.a.m.shared.release.env.ReleaseEnvironment.getL…
asfgit closed pull request #136: [MRELEASE-1098] Drop o.a.m.shared.release.env.ReleaseEnvironment.getL… URL: https://github.com/apache/maven-release/pull/136 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MRELEASE-1098) Drop o.a.m.shared.release.env.ReleaseEnvironment.getLocale()
[ https://issues.apache.org/jira/browse/MRELEASE-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRELEASE-1098. Resolution: Fixed Fixed with [9bf8fd2d0be10a24791c1994f8e668a4bab0608b|https://gitbox.apache.org/repos/asf?p=maven-release.git&a=commit&h=9bf8fd2d0be10a24791c1994f8e668a4bab0608b]. > Drop o.a.m.shared.release.env.ReleaseEnvironment.getLocale() > > > Key: MRELEASE-1098 > URL: https://issues.apache.org/jira/browse/MRELEASE-1098 > Project: Maven Release Plugin > Issue Type: Task >Affects Versions: 3.0.0-M5 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0-M6 > > > No bundles are translated, all our code is English, nothing else. Other > messages aren't even externalized. It makes no sense to provide an > unused/unusable option. See also: > https://github.com/apache/maven-release/pull/135#discussion_r884282247 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-enforcer] slawekjaranowski opened a new pull request, #159: [MENFORCER-421] Use currently build artifacts in IT tests
slawekjaranowski opened a new pull request, #159: URL: https://github.com/apache/maven-enforcer/pull/159 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MENFORCER) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MENFORCER-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MENFORCER-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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-release] michael-o commented on a diff in pull request #132: [MRELEASE-1096] Many cleanups and updates
michael-o commented on code in PR #132: URL: https://github.com/apache/maven-release/pull/132#discussion_r886007610 ## maven-release-manager/src/test/resources/pomfinder/pom1.xml: ## @@ -193,7 +193,7 @@ org.codehaus.plexus plexus-maven-plugin -1.3.8 +@plexusMavenPluginVersion@ Review Comment: Note: This likely needs to be rewritten in the future with Sisu and annotations. -- 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-1098) Drop o.a.m.shared.release.env.ReleaseEnvironment.getLocale()
[ https://issues.apache.org/jira/browse/MRELEASE-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544553#comment-17544553 ] Hudson commented on MRELEASE-1098: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-release » master #49 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/49/ > Drop o.a.m.shared.release.env.ReleaseEnvironment.getLocale() > > > Key: MRELEASE-1098 > URL: https://issues.apache.org/jira/browse/MRELEASE-1098 > Project: Maven Release Plugin > Issue Type: Task >Affects Versions: 3.0.0-M5 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0-M6 > > > No bundles are translated, all our code is English, nothing else. Other > messages aren't even externalized. It makes no sense to provide an > unused/unusable option. See also: > https://github.com/apache/maven-release/pull/135#discussion_r884282247 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-release] asfgit closed pull request #132: [MRELEASE-1096] Many cleanups and updates
asfgit closed pull request #132: [MRELEASE-1096] Many cleanups and updates URL: https://github.com/apache/maven-release/pull/132 -- 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] (MRELEASE-1096) Many cleanups and updates
[ https://issues.apache.org/jira/browse/MRELEASE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRELEASE-1096: - Summary: Many cleanups and updates (was: Cleanups and updates) > Many cleanups and updates > - > > Key: MRELEASE-1096 > URL: https://issues.apache.org/jira/browse/MRELEASE-1096 > Project: Maven Release Plugin > Issue Type: Improvement >Reporter: Niels Basjes >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0-M6 > > > In many places old plugins and related todos are open. > Several of the integration tests still use ancient dependencies. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (MRELEASE-1096) Many cleanups and updates
[ https://issues.apache.org/jira/browse/MRELEASE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRELEASE-1096. Resolution: Fixed Fixed with [281b68016dcceaded2fa9308bd07e2efa4bf747d|https://gitbox.apache.org/repos/asf?p=maven-release.git&a=commit&h=281b68016dcceaded2fa9308bd07e2efa4bf747d]. > Many cleanups and updates > - > > Key: MRELEASE-1096 > URL: https://issues.apache.org/jira/browse/MRELEASE-1096 > Project: Maven Release Plugin > Issue Type: Improvement >Reporter: Niels Basjes >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0-M6 > > > In many places old plugins and related todos are open. > Several of the integration tests still use ancient dependencies. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-release] dependabot[bot] commented on pull request #127: Bump slf4j-api from 1.7.5 to 1.7.36
dependabot[bot] commented on PR #127: URL: https://github.com/apache/maven-release/pull/127#issuecomment-1142534675 Looks like org.slf4j:slf4j-api is up-to-date now, so this is no longer needed. -- 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-release] dependabot[bot] closed pull request #127: Bump slf4j-api from 1.7.5 to 1.7.36
dependabot[bot] closed pull request #127: Bump slf4j-api from 1.7.5 to 1.7.36 URL: https://github.com/apache/maven-release/pull/127 -- 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-1072) scm.tag removed for next snapshot during prepare when using svn
[
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544565#comment-17544565
]
Michael Osipov commented on MRELEASE-1072:
--
Honestly, I will need some time to understand the problem. I still haven't.
[~hboutemy], did you understand the problem?
> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element
> (e.g. with value "trunk") this is removed during prepare for the next
> snapshot version. The tagged/release version contains the properly adjusted
> tag element.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-scm] michael-o commented on pull request #144: [SCM-925] Implement RemoveCommand in maven-scm-provider-jgit
michael-o commented on PR #144: URL: https://github.com/apache/maven-scm/pull/144#issuecomment-1142537483 @G-Ork Please have a look at my comments. I want to finalize this PR. -- 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] (SCM-925) RemoveCommand unsupported - maven-release-plugin:prepare-with-pom failing
[ https://issues.apache.org/jira/browse/SCM-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544566#comment-17544566 ] ASF GitHub Bot commented on SCM-925: michael-o commented on PR #144: URL: https://github.com/apache/maven-scm/pull/144#issuecomment-1142537483 @G-Ork Please have a look at my comments. I want to finalize this PR. > RemoveCommand unsupported - maven-release-plugin:prepare-with-pom failing > - > > Key: SCM-925 > URL: https://issues.apache.org/jira/browse/SCM-925 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-jgit >Affects Versions: 1.11.2 >Reporter: Georg Tsakumagos >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0-M2 > > Attachments: maven-scm-provider-jgit.log > > Time Spent: 10m > Remaining Estimate: 0h > > The git scm plugins differs in support for the scm command _remove_. This > breaks the goal _prepare-with-pom_ of the _maven-release-plugin_ using the > _maven-scm-provider-jgit_. The method is not fully implemented and throws an > UnsupportedOperationException. > Referring to the ["Maven SCM Providers > Matrix"|https://maven.apache.org/scm/matrix.html] this feature is documented > as supported and should be implemented in the _jgit_ provider like in > maven-scm-provider-gitexe. > > ||Variant||remove supported||Source|| > |maven-scm-provider-gitexe|(/)|[Github - GitExeScmProvider.java - > getRemoveCommand()|https://github.com/apache/maven-scm/blob/a1f7e9857076940c878a370ff599b394df768d33/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/GitExeScmProvider.java#L97]| > |maven-scm-provider-jgit|(x)|[Github - JGitScmProvider.java - > getRemoveCommand()|https://github.com/apache/maven-scm/blob/a1f7e9857076940c878a370ff599b394df768d33/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/src/main/java/org/apache/maven/scm/provider/git/jgit/JGitScmProvider.java#L113]| > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-scm] michael-o commented on a diff in pull request #150: [SCM-939] Towards JUnit4 ... DRAFT !!
michael-o commented on code in PR #150:
URL: https://github.com/apache/maven-scm/pull/150#discussion_r886032110
##
maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/BranchMojoTest.java:
##
@@ -79,36 +85,33 @@ protected void setUp()
checkoutMojo.execute();
}
+@Test
public void testBranch()
throws Exception
{
-if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
-{
-ScmTestCase.printSystemCmdUnavail(
SvnScmTestUtils.SVN_COMMAND_LINE, getName() );
-return;
-}
+checkScmPresence( SvnScmTestUtils.SVNADMIN_COMMAND_LINE, "testBranch"
);
BranchMojo mojo =
-(BranchMojo) lookupMojo( "branch", getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
+(BranchMojo) lookupMojo( "branch",
PlexusJUnit4TestSupport.getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
Review Comment:
Why not have the method in the parent class thorugh delegation?
--
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] (SCM-939) Assume SCM is present
[
https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544567#comment-17544567
]
ASF GitHub Bot commented on SCM-939:
michael-o commented on code in PR #150:
URL: https://github.com/apache/maven-scm/pull/150#discussion_r886032110
##
maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/BranchMojoTest.java:
##
@@ -79,36 +85,33 @@ protected void setUp()
checkoutMojo.execute();
}
+@Test
public void testBranch()
throws Exception
{
-if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
-{
-ScmTestCase.printSystemCmdUnavail(
SvnScmTestUtils.SVN_COMMAND_LINE, getName() );
-return;
-}
+checkScmPresence( SvnScmTestUtils.SVNADMIN_COMMAND_LINE, "testBranch"
);
BranchMojo mojo =
-(BranchMojo) lookupMojo( "branch", getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
+(BranchMojo) lookupMojo( "branch",
PlexusJUnit4TestSupport.getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
Review Comment:
Why not have the method in the parent class thorugh delegation?
> Assume SCM is present
> -
>
> Key: SCM-939
> URL: https://issues.apache.org/jira/browse/SCM-939
> Project: Maven SCM
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> We have a lot of tests that do something like this:
>
> if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
> {
> ScmTestCase.printSystemCmdUnavail( SvnScmTestUtils.SVN_COMMAND_LINE,
> getName() );
> return;
> }
>
> We should instead use org.*junit*.*Assume* here so these are marked as
> skipped rather than passed.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (SCM-990) Jgit Provider cannot resolve Repository in multi-module Maven Project
[
https://issues.apache.org/jira/browse/SCM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544569#comment-17544569
]
Michael Osipov commented on SCM-990:
What about:
https://www.codeaffine.com/2014/09/22/access-git-repository-with-jgit/
{code:java}
https://www.codeaffine.com/2014/09/22/access-git-repository-with-jgit/
{code}
> Jgit Provider cannot resolve Repository in multi-module Maven Project
> -
>
> Key: SCM-990
> URL: https://issues.apache.org/jira/browse/SCM-990
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-jgit
>Reporter: Enrico Horn
>Priority: Major
>
> The JGit providers info command (and probably others) uses fielset.basedir as
> git working directory. When running maven command in a submodule this will
> result in the following error:
>
> Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. JGit resolve failure!
> repository not found:
>
> What it should do instead is act like the git binary and search for the git
> directory in parent directories if none found in the current one. Jgit has
> the API FileRepositoryBuilder.findGitDir to do that.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-scm] nielsbasjes commented on a diff in pull request #150: [SCM-939] Towards JUnit4 ... DRAFT !!
nielsbasjes commented on code in PR #150:
URL: https://github.com/apache/maven-scm/pull/150#discussion_r886035241
##
maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/BranchMojoTest.java:
##
@@ -79,36 +85,33 @@ protected void setUp()
checkoutMojo.execute();
}
+@Test
public void testBranch()
throws Exception
{
-if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
-{
-ScmTestCase.printSystemCmdUnavail(
SvnScmTestUtils.SVN_COMMAND_LINE, getName() );
-return;
-}
+checkScmPresence( SvnScmTestUtils.SVNADMIN_COMMAND_LINE, "testBranch"
);
BranchMojo mojo =
-(BranchMojo) lookupMojo( "branch", getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
+(BranchMojo) lookupMojo( "branch",
PlexusJUnit4TestSupport.getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
Review Comment:
Because this is a very incomplete draft.
My first goal was to make it work an then restructure to make it clean.
I have note been able to reach this first goal yet.
--
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] [Comment Edited] (SCM-990) Jgit Provider cannot resolve Repository in multi-module Maven Project
[
https://issues.apache.org/jira/browse/SCM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544569#comment-17544569
]
Michael Osipov edited comment on SCM-990 at 5/31/22 7:08 PM:
-
What about:
https://www.codeaffine.com/2014/09/22/access-git-repository-with-jgit/
{code:java}
repositoryBuilder.findGitDir( new File( "/home/user/git/foo/bar" ) );
{code}
was (Author: michael-o):
What about:
https://www.codeaffine.com/2014/09/22/access-git-repository-with-jgit/
{code:java}
https://www.codeaffine.com/2014/09/22/access-git-repository-with-jgit/
{code}
> Jgit Provider cannot resolve Repository in multi-module Maven Project
> -
>
> Key: SCM-990
> URL: https://issues.apache.org/jira/browse/SCM-990
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-jgit
>Reporter: Enrico Horn
>Priority: Major
>
> The JGit providers info command (and probably others) uses fielset.basedir as
> git working directory. When running maven command in a submodule this will
> result in the following error:
>
> Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. JGit resolve failure!
> repository not found:
>
> What it should do instead is act like the git binary and search for the git
> directory in parent directories if none found in the current one. Jgit has
> the API FileRepositoryBuilder.findGitDir to do that.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (SCM-939) Assume SCM is present
[
https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544570#comment-17544570
]
ASF GitHub Bot commented on SCM-939:
nielsbasjes commented on code in PR #150:
URL: https://github.com/apache/maven-scm/pull/150#discussion_r886035241
##
maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/BranchMojoTest.java:
##
@@ -79,36 +85,33 @@ protected void setUp()
checkoutMojo.execute();
}
+@Test
public void testBranch()
throws Exception
{
-if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
-{
-ScmTestCase.printSystemCmdUnavail(
SvnScmTestUtils.SVN_COMMAND_LINE, getName() );
-return;
-}
+checkScmPresence( SvnScmTestUtils.SVNADMIN_COMMAND_LINE, "testBranch"
);
BranchMojo mojo =
-(BranchMojo) lookupMojo( "branch", getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
+(BranchMojo) lookupMojo( "branch",
PlexusJUnit4TestSupport.getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
Review Comment:
Because this is a very incomplete draft.
My first goal was to make it work an then restructure to make it clean.
I have note been able to reach this first goal yet.
> Assume SCM is present
> -
>
> Key: SCM-939
> URL: https://issues.apache.org/jira/browse/SCM-939
> Project: Maven SCM
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> We have a lot of tests that do something like this:
>
> if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
> {
> ScmTestCase.printSystemCmdUnavail( SvnScmTestUtils.SVN_COMMAND_LINE,
> getName() );
> return;
> }
>
> We should instead use org.*junit*.*Assume* here so these are marked as
> skipped rather than passed.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-scm] michael-o commented on pull request #150: [SCM-939] Towards JUnit4 ... DRAFT !!
michael-o commented on PR #150: URL: https://github.com/apache/maven-scm/pull/150#issuecomment-1142545754 @cstamas WDYT? -- 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] (SCM-939) Assume SCM is present
[
https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544571#comment-17544571
]
ASF GitHub Bot commented on SCM-939:
michael-o commented on PR #150:
URL: https://github.com/apache/maven-scm/pull/150#issuecomment-1142545754
@cstamas WDYT?
> Assume SCM is present
> -
>
> Key: SCM-939
> URL: https://issues.apache.org/jira/browse/SCM-939
> Project: Maven SCM
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> We have a lot of tests that do something like this:
>
> if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
> {
> ScmTestCase.printSystemCmdUnavail( SvnScmTestUtils.SVN_COMMAND_LINE,
> getName() );
> return;
> }
>
> We should instead use org.*junit*.*Assume* here so these are marked as
> skipped rather than passed.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-surefire] dependabot[bot] opened a new pull request, #541: Bump assertj-core from 3.22.0 to 3.23.1
dependabot[bot] opened a new pull request, #541: URL: https://github.com/apache/maven-surefire/pull/541 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.22.0 to 3.23.1. Commits https://github.com/assertj/assertj-core/commit/0256688fcf02d7c1c1940b1226a24fb5680ac3a3";>0256688 [maven-release-plugin] prepare release assertj-core-3.23.1 https://github.com/assertj/assertj-core/commit/6529933700533de4e8f8191d9b6f4ef371667f1d";>6529933 Downgrade junit-jupiter from 5.9.0-M1 to 5.8.2 https://github.com/assertj/assertj-core/commit/d9cd2da03acd4d68a5599b61fdd9abd5da0cc7be";>d9cd2da [maven-release-plugin] prepare for next development iteration https://github.com/assertj/assertj-core/commit/6f19754e579527b935c9e62d5cb5b0900fa1e6a1";>6f19754 [maven-release-plugin] prepare release assertj-core-3.23.0 https://github.com/assertj/assertj-core/commit/c592c18a59a1ef4f681f1eb08b2571fa77757e43";>c592c18 Expose ComparisonStrategy::areEqual in AbstractAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2633";>#2633) https://github.com/assertj/assertj-core/commit/69c66a9bb66f8b8a39535eb769e8c97d0d8c6648";>69c66a9 Bump maven-invoker-plugin from 3.2.2 to 3.3.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2636";>#2636) https://github.com/assertj/assertj-core/commit/795f5278bebb2703eda7b11569403c2bed650d5a";>795f527 Fix test https://github.com/assertj/assertj-core/commit/b44460623b9c0e83c2b311c1fc6b7bffa1a077b9";>b444606 Bump hibernate-core from 6.0.1.Final to 6.0.2.Final (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2626";>#2626) https://github.com/assertj/assertj-core/commit/793241125ee85ac832a6ee12fc77456256c5";>7932411 Fix typos in Javadoc of ObjectEnumerableAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2624";>#2624) https://github.com/assertj/assertj-core/commit/b746e6aeb4b9bd7246797c3fc18059977aac6ab3";>b746e6a [mvn] Update maven wrapper to 3.1.1 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2622";>#2622) Additional commits viewable in https://github.com/assertj/assertj-core/compare/assertj-core-3.22.0...assertj-core-3.23.1";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-release] michael-o commented on pull request #104: [MRELEASE-1078] Conventional commits
michael-o commented on PR #104: URL: https://github.com/apache/maven-release/pull/104#issuecomment-1142559055 Since this requires SCM 2, I'd recommend to try out the current snapshot of SCM 2 on top of this master. I know, that there will be failures... -- 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-1096) Many cleanups and updates
[ https://issues.apache.org/jira/browse/MRELEASE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544587#comment-17544587 ] Hudson commented on MRELEASE-1096: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-release » master #50 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/50/ > Many cleanups and updates > - > > Key: MRELEASE-1096 > URL: https://issues.apache.org/jira/browse/MRELEASE-1096 > Project: Maven Release Plugin > Issue Type: Improvement >Reporter: Niels Basjes >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0-M6 > > > In many places old plugins and related todos are open. > Several of the integration tests still use ancient dependencies. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-scm] nielsbasjes commented on a diff in pull request #150: [SCM-939] Towards JUnit4 ... DRAFT !!
nielsbasjes commented on code in PR #150:
URL: https://github.com/apache/maven-scm/pull/150#discussion_r886110692
##
maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/BranchMojoTest.java:
##
@@ -79,36 +85,33 @@ protected void setUp()
checkoutMojo.execute();
}
+@Test
public void testBranch()
throws Exception
{
-if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
-{
-ScmTestCase.printSystemCmdUnavail(
SvnScmTestUtils.SVN_COMMAND_LINE, getName() );
-return;
-}
+checkScmPresence( SvnScmTestUtils.SVNADMIN_COMMAND_LINE, "testBranch"
);
BranchMojo mojo =
-(BranchMojo) lookupMojo( "branch", getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
+(BranchMojo) lookupMojo( "branch",
PlexusJUnit4TestSupport.getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
Review Comment:
So just to be clear. I'm totally fine if you guys pick this one up.
I'm stuck here.
--
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] (SCM-939) Assume SCM is present
[
https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544595#comment-17544595
]
ASF GitHub Bot commented on SCM-939:
nielsbasjes commented on code in PR #150:
URL: https://github.com/apache/maven-scm/pull/150#discussion_r886110692
##
maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/BranchMojoTest.java:
##
@@ -79,36 +85,33 @@ protected void setUp()
checkoutMojo.execute();
}
+@Test
public void testBranch()
throws Exception
{
-if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
-{
-ScmTestCase.printSystemCmdUnavail(
SvnScmTestUtils.SVN_COMMAND_LINE, getName() );
-return;
-}
+checkScmPresence( SvnScmTestUtils.SVNADMIN_COMMAND_LINE, "testBranch"
);
BranchMojo mojo =
-(BranchMojo) lookupMojo( "branch", getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
+(BranchMojo) lookupMojo( "branch",
PlexusJUnit4TestSupport.getTestFile(
"src/test/resources/mojos/branch/branch.xml" ) );
Review Comment:
So just to be clear. I'm totally fine if you guys pick this one up.
I'm stuck here.
> Assume SCM is present
> -
>
> Key: SCM-939
> URL: https://issues.apache.org/jira/browse/SCM-939
> Project: Maven SCM
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> We have a lot of tests that do something like this:
>
> if ( !ScmTestCase.isSystemCmd( SvnScmTestUtils.SVN_COMMAND_LINE ) )
> {
> ScmTestCase.printSystemCmdUnavail( SvnScmTestUtils.SVN_COMMAND_LINE,
> getName() );
> return;
> }
>
> We should instead use org.*junit*.*Assume* here so these are marked as
> skipped rather than passed.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MENFORCER-394) DependencyConvergence in 3.0.0 fails on provided scoped dependencies
[
https://issues.apache.org/jira/browse/MENFORCER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544634#comment-17544634
]
Matt Nelson commented on MENFORCER-394:
---
Noticing some odd behavior trying to verify this change.
The scope of transitive dependencies appear to be converted from provided to
runtime.
{noformat}
Dependency convergence error for
org.robolectric:android-all:jar:12-robolectric-7732740:runtime paths to
dependency are:
+-company:module:jar:0.85-SNAPSHOT
+-company:other-module:jar:3.0:compile
+-dnsjava:dnsjava:jar:3.5.1:compile
+-org.robolectric:android-all:jar:12-robolectric-7732740:runtime
and
+-company:module:jar:0.85-SNAPSHOT
+-io.fabric8:kubernetes-client:jar:5.12.2:runtime
+-com.squareup.okhttp3:okhttp:jar:3.14.9:runtime
+-org.robolectric:android-all:jar:10-robolectric-5803371:runtime
{noformat}
[https://search.maven.org/artifact/dnsjava/dnsjava/3.5.1/bundle]
{code:xml}
org.robolectric
android-all
12-robolectric-7732740
provided
{code}
[https://search.maven.org/artifact/io.fabric8/kubernetes-client/5.12.2/jar]
default scope of compile
{code:xml}
com.squareup.okhttp3
okhttp
${okhttp.version}
{code}
[https://search.maven.org/artifact/com.squareup.okhttp3/okhttp/3.14.9/jar]
{code:xml}
org.robolectric
android-all
provided
{code}
> DependencyConvergence in 3.0.0 fails on provided scoped dependencies
>
>
> Key: MENFORCER-394
> URL: https://issues.apache.org/jira/browse/MENFORCER-394
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
>Affects Versions: 3.0.0
>Reporter: Joe Barnett
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.0.1
>
>
> In our project, using version 3.0.0-M3 of the maven-enforcer-plugin's
> DependencyConvergence rule passes. Using version 3.0.0 starts to show
> convergence errors where provided scope dependencies have different versions
> than compile scope dependencies, for example:
> {code:java}
> [WARNING]
> Dependency convergence error for
> org.javassist:javassist:jar:3.28.0-GA:compile paths to dependency are:
> +-com.trib3:testing:jar:1.25-dependabot-maven-org.apache.maven.plugins-maven-enforcer-plugin-3.0.0-SNAPSHOT
> +-io.dropwizard:dropwizard-auth:jar:2.0.23:compile
> +-io.dropwizard:dropwizard-jersey:jar:2.0.23:compile
> +-org.javassist:javassist:jar:3.28.0-GA:compile
> and
> +-com.trib3:testing:jar:1.25-dependabot-maven-org.apache.maven.plugins-maven-enforcer-plugin-3.0.0-SNAPSHOT
> +-io.dropwizard:dropwizard-testing:jar:2.0.23:compile
> +-org.hibernate:hibernate-core:jar:5.5.2.Final:provided
> +-org.javassist:javassist:jar:3.27.0-GA:provided
> {code}
> Is this an intended breaking change? I don't see anything in the release
> announcement that points obviously to a change here. Seems like the provided
> version shouldn't matter as it doesn't get shipped with the artifact?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn
[
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544638#comment-17544638
]
Herve Boutemy commented on MRELEASE-1072:
-
it's not a bug, it's a new feature: you're trying to do something that was
never done/intended
abstract description is too abstract
please show concrete scm configuration you're wanting to support
> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element
> (e.g. with value "trunk") this is removed during prepare for the next
> snapshot version. The tagged/release version contains the properly adjusted
> tag element.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn
[
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544638#comment-17544638
]
Herve Boutemy edited comment on MRELEASE-1072 at 5/31/22 11:12 PM:
---
it's not a bug, it's a new feature: you're trying to do something that was
never done/intended (and for svn that we used for years, and don't really use
any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support
was (Author: hboutemy):
it's not a bug, it's a new feature: you're trying to do something that was
never done/intended
abstract description is too abstract
please show concrete scm configuration you're wanting to support
> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element
> (e.g. with value "trunk") this is removed during prepare for the next
> snapshot version. The tagged/release version contains the properly adjusted
> tag element.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn
[
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544638#comment-17544638
]
Herve Boutemy edited comment on MRELEASE-1072 at 5/31/22 11:12 PM:
---
it's not a bug, it's a new feature: you're trying to do something that was
never done/intended (and for svn that we used for years with ho problem, and
don't really use any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support
was (Author: hboutemy):
it's not a bug, it's a new feature: you're trying to do something that was
never done/intended (and for svn that we used for years, and don't really use
any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support
> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element
> (e.g. with value "trunk") this is removed during prepare for the next
> snapshot version. The tagged/release version contains the properly adjusted
> tag element.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn
[
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544638#comment-17544638
]
Herve Boutemy edited comment on MRELEASE-1072 at 5/31/22 11:21 PM:
---
it's not a bug, it's a new feature: you're trying to do something that was
never done/intended (and for svn that we used for years with no problem, and
don't really use any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support, ideally also
with link to some live svn repositories
was (Author: hboutemy):
it's not a bug, it's a new feature: you're trying to do something that was
never done/intended (and for svn that we used for years with ho problem, and
don't really use any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support
> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element
> (e.g. with value "trunk") this is removed during prepare for the next
> snapshot version. The tagged/release version contains the properly adjusted
> tag element.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-javadoc-plugin] dependabot[bot] opened a new pull request, #143: Bump assertj-core from 3.21.0 to 3.23.1
dependabot[bot] opened a new pull request, #143: URL: https://github.com/apache/maven-javadoc-plugin/pull/143 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.21.0 to 3.23.1. Commits https://github.com/assertj/assertj-core/commit/0256688fcf02d7c1c1940b1226a24fb5680ac3a3";>0256688 [maven-release-plugin] prepare release assertj-core-3.23.1 https://github.com/assertj/assertj-core/commit/6529933700533de4e8f8191d9b6f4ef371667f1d";>6529933 Downgrade junit-jupiter from 5.9.0-M1 to 5.8.2 https://github.com/assertj/assertj-core/commit/d9cd2da03acd4d68a5599b61fdd9abd5da0cc7be";>d9cd2da [maven-release-plugin] prepare for next development iteration https://github.com/assertj/assertj-core/commit/6f19754e579527b935c9e62d5cb5b0900fa1e6a1";>6f19754 [maven-release-plugin] prepare release assertj-core-3.23.0 https://github.com/assertj/assertj-core/commit/c592c18a59a1ef4f681f1eb08b2571fa77757e43";>c592c18 Expose ComparisonStrategy::areEqual in AbstractAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2633";>#2633) https://github.com/assertj/assertj-core/commit/69c66a9bb66f8b8a39535eb769e8c97d0d8c6648";>69c66a9 Bump maven-invoker-plugin from 3.2.2 to 3.3.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2636";>#2636) https://github.com/assertj/assertj-core/commit/795f5278bebb2703eda7b11569403c2bed650d5a";>795f527 Fix test https://github.com/assertj/assertj-core/commit/b44460623b9c0e83c2b311c1fc6b7bffa1a077b9";>b444606 Bump hibernate-core from 6.0.1.Final to 6.0.2.Final (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2626";>#2626) https://github.com/assertj/assertj-core/commit/793241125ee85ac832a6ee12fc77456256c5";>7932411 Fix typos in Javadoc of ObjectEnumerableAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2624";>#2624) https://github.com/assertj/assertj-core/commit/b746e6aeb4b9bd7246797c3fc18059977aac6ab3";>b746e6a [mvn] Update maven wrapper to 3.1.1 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2622";>#2622) Additional commits viewable in https://github.com/assertj/assertj-core/compare/assertj-core-3.21.0...assertj-core-3.23.1";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-javadoc-plugin] dependabot[bot] closed pull request #142: Bump assertj-core from 3.21.0 to 3.23.0
dependabot[bot] closed pull request #142: Bump assertj-core from 3.21.0 to 3.23.0 URL: https://github.com/apache/maven-javadoc-plugin/pull/142 -- 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-javadoc-plugin] dependabot[bot] commented on pull request #142: Bump assertj-core from 3.21.0 to 3.23.0
dependabot[bot] commented on PR #142: URL: https://github.com/apache/maven-javadoc-plugin/pull/142#issuecomment-1143115530 Superseded by #143. -- 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-surefire] olamy commented on pull request #535: [SUREFIRE-2086] Management of temporary files
olamy commented on PR #535: URL: https://github.com/apache/maven-surefire/pull/535#issuecomment-1143133867 @sman-81 not sure what you have done but this PR include plenty of non needed commits (already in master) you should rebase correctly from master thanks -- 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-analyzer] dependabot[bot] commented on pull request #64: Bump assertj-core from 3.22.0 to 3.23.0
dependabot[bot] commented on PR #64: URL: https://github.com/apache/maven-dependency-analyzer/pull/64#issuecomment-1143153165 Superseded by #65. -- 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-analyzer] dependabot[bot] opened a new pull request, #65: Bump assertj-core from 3.22.0 to 3.23.1
dependabot[bot] opened a new pull request, #65: URL: https://github.com/apache/maven-dependency-analyzer/pull/65 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.22.0 to 3.23.1. Commits https://github.com/assertj/assertj-core/commit/0256688fcf02d7c1c1940b1226a24fb5680ac3a3";>0256688 [maven-release-plugin] prepare release assertj-core-3.23.1 https://github.com/assertj/assertj-core/commit/6529933700533de4e8f8191d9b6f4ef371667f1d";>6529933 Downgrade junit-jupiter from 5.9.0-M1 to 5.8.2 https://github.com/assertj/assertj-core/commit/d9cd2da03acd4d68a5599b61fdd9abd5da0cc7be";>d9cd2da [maven-release-plugin] prepare for next development iteration https://github.com/assertj/assertj-core/commit/6f19754e579527b935c9e62d5cb5b0900fa1e6a1";>6f19754 [maven-release-plugin] prepare release assertj-core-3.23.0 https://github.com/assertj/assertj-core/commit/c592c18a59a1ef4f681f1eb08b2571fa77757e43";>c592c18 Expose ComparisonStrategy::areEqual in AbstractAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2633";>#2633) https://github.com/assertj/assertj-core/commit/69c66a9bb66f8b8a39535eb769e8c97d0d8c6648";>69c66a9 Bump maven-invoker-plugin from 3.2.2 to 3.3.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2636";>#2636) https://github.com/assertj/assertj-core/commit/795f5278bebb2703eda7b11569403c2bed650d5a";>795f527 Fix test https://github.com/assertj/assertj-core/commit/b44460623b9c0e83c2b311c1fc6b7bffa1a077b9";>b444606 Bump hibernate-core from 6.0.1.Final to 6.0.2.Final (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2626";>#2626) https://github.com/assertj/assertj-core/commit/793241125ee85ac832a6ee12fc77456256c5";>7932411 Fix typos in Javadoc of ObjectEnumerableAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2624";>#2624) https://github.com/assertj/assertj-core/commit/b746e6aeb4b9bd7246797c3fc18059977aac6ab3";>b746e6a [mvn] Update maven wrapper to 3.1.1 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2622";>#2622) Additional commits viewable in https://github.com/assertj/assertj-core/compare/assertj-core-3.22.0...assertj-core-3.23.1";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-analyzer] dependabot[bot] closed pull request #64: Bump assertj-core from 3.22.0 to 3.23.0
dependabot[bot] closed pull request #64: Bump assertj-core from 3.22.0 to 3.23.0 URL: https://github.com/apache/maven-dependency-analyzer/pull/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
[GitHub] [maven-enforcer] slawekjaranowski merged pull request #159: [MENFORCER-421] Use currently build artifacts in IT tests
slawekjaranowski merged PR #159: URL: https://github.com/apache/maven-enforcer/pull/159 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MENFORCER-421) Use currently build artifacts in IT tests
[
https://issues.apache.org/jira/browse/MENFORCER-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed MENFORCER-421.
-
Resolution: Fixed
> Use currently build artifacts in IT tests
> -
>
> Key: MENFORCER-421
> URL: https://issues.apache.org/jira/browse/MENFORCER-421
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.0.1
>
>
> Due to misconfigured of {{mrm-maven-plugin}} during IT test artifacts from
> previous build are used or downloaded from remote repository.
> {{localRepo}} of {{mrm-maven-plugin}} should be used with the same directory
> as used for {{localRepositoryPath}} of maven-invoker-plugin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-invoker-plugin] dependabot[bot] opened a new pull request, #127: Bump groovy-version from 3.0.10 to 3.0.11
dependabot[bot] opened a new pull request, #127: URL: https://github.com/apache/maven-invoker-plugin/pull/127 Bumps `groovy-version` from 3.0.10 to 3.0.11. Updates `groovy` from 3.0.10 to 3.0.11 Commits See full diff in https://github.com/apache/groovy/commits";>compare view Updates `groovy-json` from 3.0.10 to 3.0.11 Commits See full diff in https://github.com/apache/groovy/commits";>compare view Updates `groovy-xml` from 3.0.10 to 3.0.11 Commits See full diff in https://github.com/apache/groovy/commits";>compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-invoker-plugin] dependabot[bot] opened a new pull request, #128: Bump assertj-core from 3.22.0 to 3.23.1
dependabot[bot] opened a new pull request, #128: URL: https://github.com/apache/maven-invoker-plugin/pull/128 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.22.0 to 3.23.1. Commits https://github.com/assertj/assertj-core/commit/0256688fcf02d7c1c1940b1226a24fb5680ac3a3";>0256688 [maven-release-plugin] prepare release assertj-core-3.23.1 https://github.com/assertj/assertj-core/commit/6529933700533de4e8f8191d9b6f4ef371667f1d";>6529933 Downgrade junit-jupiter from 5.9.0-M1 to 5.8.2 https://github.com/assertj/assertj-core/commit/d9cd2da03acd4d68a5599b61fdd9abd5da0cc7be";>d9cd2da [maven-release-plugin] prepare for next development iteration https://github.com/assertj/assertj-core/commit/6f19754e579527b935c9e62d5cb5b0900fa1e6a1";>6f19754 [maven-release-plugin] prepare release assertj-core-3.23.0 https://github.com/assertj/assertj-core/commit/c592c18a59a1ef4f681f1eb08b2571fa77757e43";>c592c18 Expose ComparisonStrategy::areEqual in AbstractAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2633";>#2633) https://github.com/assertj/assertj-core/commit/69c66a9bb66f8b8a39535eb769e8c97d0d8c6648";>69c66a9 Bump maven-invoker-plugin from 3.2.2 to 3.3.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2636";>#2636) https://github.com/assertj/assertj-core/commit/795f5278bebb2703eda7b11569403c2bed650d5a";>795f527 Fix test https://github.com/assertj/assertj-core/commit/b44460623b9c0e83c2b311c1fc6b7bffa1a077b9";>b444606 Bump hibernate-core from 6.0.1.Final to 6.0.2.Final (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2626";>#2626) https://github.com/assertj/assertj-core/commit/793241125ee85ac832a6ee12fc77456256c5";>7932411 Fix typos in Javadoc of ObjectEnumerableAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2624";>#2624) https://github.com/assertj/assertj-core/commit/b746e6aeb4b9bd7246797c3fc18059977aac6ab3";>b746e6a [mvn] Update maven wrapper to 3.1.1 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2622";>#2622) Additional commits viewable in https://github.com/assertj/assertj-core/compare/assertj-core-3.22.0...assertj-core-3.23.1";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-invoker-plugin] dependabot[bot] closed pull request #126: Bump assertj-core from 3.22.0 to 3.23.0
dependabot[bot] closed pull request #126: Bump assertj-core from 3.22.0 to 3.23.0 URL: https://github.com/apache/maven-invoker-plugin/pull/126 -- 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-invoker-plugin] dependabot[bot] commented on pull request #126: Bump assertj-core from 3.22.0 to 3.23.0
dependabot[bot] commented on PR #126: URL: https://github.com/apache/maven-invoker-plugin/pull/126#issuecomment-1143164392 Superseded by #128. -- 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-surefire] sman-81 commented on pull request #535: [SUREFIRE-2086] Management of temporary files
sman-81 commented on PR #535: URL: https://github.com/apache/maven-surefire/pull/535#issuecomment-1143166333 > @sman-81 not sure what you have done but this PR include plenty of non needed commits (already in master) plenty of changes are not from you. maybe you should rebase correctly from master. thanks @olamy I had done the rebase from master wrongly. Now it should be good. Could you please take another look? -- 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, #110: Bump assertj-core from 3.21.0 to 3.23.1
dependabot[bot] opened a new pull request, #110: URL: https://github.com/apache/maven-jlink-plugin/pull/110 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.21.0 to 3.23.1. Commits https://github.com/assertj/assertj-core/commit/0256688fcf02d7c1c1940b1226a24fb5680ac3a3";>0256688 [maven-release-plugin] prepare release assertj-core-3.23.1 https://github.com/assertj/assertj-core/commit/6529933700533de4e8f8191d9b6f4ef371667f1d";>6529933 Downgrade junit-jupiter from 5.9.0-M1 to 5.8.2 https://github.com/assertj/assertj-core/commit/d9cd2da03acd4d68a5599b61fdd9abd5da0cc7be";>d9cd2da [maven-release-plugin] prepare for next development iteration https://github.com/assertj/assertj-core/commit/6f19754e579527b935c9e62d5cb5b0900fa1e6a1";>6f19754 [maven-release-plugin] prepare release assertj-core-3.23.0 https://github.com/assertj/assertj-core/commit/c592c18a59a1ef4f681f1eb08b2571fa77757e43";>c592c18 Expose ComparisonStrategy::areEqual in AbstractAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2633";>#2633) https://github.com/assertj/assertj-core/commit/69c66a9bb66f8b8a39535eb769e8c97d0d8c6648";>69c66a9 Bump maven-invoker-plugin from 3.2.2 to 3.3.0 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2636";>#2636) https://github.com/assertj/assertj-core/commit/795f5278bebb2703eda7b11569403c2bed650d5a";>795f527 Fix test https://github.com/assertj/assertj-core/commit/b44460623b9c0e83c2b311c1fc6b7bffa1a077b9";>b444606 Bump hibernate-core from 6.0.1.Final to 6.0.2.Final (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2626";>#2626) https://github.com/assertj/assertj-core/commit/793241125ee85ac832a6ee12fc77456256c5";>7932411 Fix typos in Javadoc of ObjectEnumerableAssert (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2624";>#2624) https://github.com/assertj/assertj-core/commit/b746e6aeb4b9bd7246797c3fc18059977aac6ab3";>b746e6a [mvn] Update maven wrapper to 3.1.1 (https://github-redirect.dependabot.com/assertj/assertj-core/issues/2622";>#2622) Additional commits viewable in https://github.com/assertj/assertj-core/compare/assertj-core-3.21.0...assertj-core-3.23.1";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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] closed pull request #109: Bump assertj-core from 3.21.0 to 3.23.0
dependabot[bot] closed pull request #109: Bump assertj-core from 3.21.0 to 3.23.0 URL: https://github.com/apache/maven-jlink-plugin/pull/109 -- 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] commented on pull request #109: Bump assertj-core from 3.21.0 to 3.23.0
dependabot[bot] commented on PR #109: URL: https://github.com/apache/maven-jlink-plugin/pull/109#issuecomment-1143167267 Superseded by #110. -- 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] (MENFORCER-421) Use currently build artifacts in IT tests
[
https://issues.apache.org/jira/browse/MENFORCER-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544725#comment-17544725
]
Hudson commented on MENFORCER-421:
--
Build failed in Jenkins: Maven » Maven TLP » maven-enforcer » master #30
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/30/
> Use currently build artifacts in IT tests
> -
>
> Key: MENFORCER-421
> URL: https://issues.apache.org/jira/browse/MENFORCER-421
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.0.1
>
>
> Due to misconfigured of {{mrm-maven-plugin}} during IT test artifacts from
> previous build are used or downloaded from remote repository.
> {{localRepo}} of {{mrm-maven-plugin}} should be used with the same directory
> as used for {{localRepositoryPath}} of maven-invoker-plugin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
