[GitHub] [maven-doxia] dependabot[bot] opened a new pull request #39: Bump ant-apache-regexp from 1.7.1 to 1.10.9
dependabot[bot] opened a new pull request #39: URL: https://github.com/apache/maven-doxia/pull/39 Bumps ant-apache-regexp from 1.7.1 to 1.10.9. [](https://docs.github.com/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates) 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-doxia-site] dependabot[bot] opened a new pull request #10: Bump ant from 1.10.8 to 1.10.9
dependabot[bot] opened a new pull request #10: URL: https://github.com/apache/maven-doxia-site/pull/10 Bumps ant from 1.10.8 to 1.10.9. [](https://docs.github.com/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates) 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Unexpected dependency requirement when performing "package", but not "install"
Of course, I will do it when I get to the office tomorrow, thanks! - Eric L On Wed, Sep 30, 2020 at 5:51 PM Elliotte Rusty Harold wrote: > Looks like we don't need that. Can you file a bug in Jira? > > On Wed, Sep 30, 2020 at 11:12 AM Eric Lilja wrote: > > > > Hello, I have to set up Maven on a system which is completely offline, > > restricted to work on a few, select projects. > > > > During testing, everything initially looked good, I could perform "mvn > > clean install" in all projects without issue, and could perform other > > Maven-task as well, Intellij was happy, it could resolve all projects > > fully, run all test cases etc, and did not complain about any missing > > artifacts. > > > > However, then I noticed, almost by accident, that I couldn't do "package" > > or "verify" (which was odd, since install works, which is a later > phase!), > > because then surefire (3.0.0-M5) would complain it was > > missing org.apache.maven:maven-toolchain:jar:3.0-alpha-2 (or one of its > > dependencies). > > > > Why Surefire would suddenly need that artifact (some old alpha from > > 2009..), during package- or verify-phase feels weird to me since the > later > > phase, install, works, and install entails packaging and verification > > (compile also works, btw) > > > > surefire-3.0.0-M3 also suffers from this issue...2.18.1 does not > > > > What's going on here? Is my analysis correct, that if I can do "mvn clean > > install", then "mvn clean package" should not be an issue, since installs > > entails packaging? > > > > For this exotic setup, we can easily work around this, obviously, but it > > feels like a bug to me so I wanted to share it with you > > > > - Eric L > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Unexpected dependency requirement when performing "package", but not "install"
Looks like we don't need that. Can you file a bug in Jira? On Wed, Sep 30, 2020 at 11:12 AM Eric Lilja wrote: > > Hello, I have to set up Maven on a system which is completely offline, > restricted to work on a few, select projects. > > During testing, everything initially looked good, I could perform "mvn > clean install" in all projects without issue, and could perform other > Maven-task as well, Intellij was happy, it could resolve all projects > fully, run all test cases etc, and did not complain about any missing > artifacts. > > However, then I noticed, almost by accident, that I couldn't do "package" > or "verify" (which was odd, since install works, which is a later phase!), > because then surefire (3.0.0-M5) would complain it was > missing org.apache.maven:maven-toolchain:jar:3.0-alpha-2 (or one of its > dependencies). > > Why Surefire would suddenly need that artifact (some old alpha from > 2009..), during package- or verify-phase feels weird to me since the later > phase, install, works, and install entails packaging and verification > (compile also works, btw) > > surefire-3.0.0-M3 also suffers from this issue...2.18.1 does not > > What's going on here? Is my analysis correct, that if I can do "mvn clean > install", then "mvn clean package" should not be an issue, since installs > entails packaging? > > For this exotic setup, we can easily work around this, obviously, but it > feels like a bug to me so I wanted to share it with you > > - Eric L -- Elliotte Rusty Harold elh...@ibiblio.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Unexpected dependency requirement when performing "package", but not "install"
Hello, I have to set up Maven on a system which is completely offline, restricted to work on a few, select projects. During testing, everything initially looked good, I could perform "mvn clean install" in all projects without issue, and could perform other Maven-task as well, Intellij was happy, it could resolve all projects fully, run all test cases etc, and did not complain about any missing artifacts. However, then I noticed, almost by accident, that I couldn't do "package" or "verify" (which was odd, since install works, which is a later phase!), because then surefire (3.0.0-M5) would complain it was missing org.apache.maven:maven-toolchain:jar:3.0-alpha-2 (or one of its dependencies). Why Surefire would suddenly need that artifact (some old alpha from 2009..), during package- or verify-phase feels weird to me since the later phase, install, works, and install entails packaging and verification (compile also works, btw) surefire-3.0.0-M3 also suffers from this issue...2.18.1 does not What's going on here? Is my analysis correct, that if I can do "mvn clean install", then "mvn clean package" should not be an issue, since installs entails packaging? For this exotic setup, we can easily work around this, obviously, but it feels like a bug to me so I wanted to share it with you - Eric L
[RESULT] [VOTE] Release Apache Maven EAR Plugin version 3.1.0
Hi, The vote has passed with the following result: +1 : Marat Abrarov, Karl Heinz Marbaise, Michael Osipov, Hervé Boutemy PMC quorum reached I will promote the artifacts to the central repo. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
