Second review for MNG-6118
Hi all, Over the last month, Martin Kanters and myself have been working to make it possible to execute goals on a specific module while building a multi-module project [1]. The pull request [2] enables resolving inter-module dependencies of the whole multi-module project while building a part of a multi-module project (by using -f or by navigating to a subdirectory). These changes make the following scenarios behave in a consistent way: * mvn -pl module-a * mvn -f module-a/pom.xml * cd module-a && mvn There are also integration tests [3] that demonstrate and verify this behaviour. The changes have run through Jenkins in an earlier stage, and are running again now that I have merged master into our feature branch. Robert has done a first round of review and we would appreciate if somebody else could also take a look at the proposed changes. Thanks, Maarten [1] https://issues.apache.org/jira/browse/MNG-6118 [2] https://github.com/apache/maven/pull/373 [3] https://github.com/apache/maven-integration-testing/pull/68 - 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"
I opened https://issues.apache.org/jira/browse/SUREFIRE-1850 Thanks! - Eric L On Wed, Sep 30, 2020 at 11:30 PM Eric Lilja wrote: > 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 >> >>
[ANN] Apache Maven EAR Plugin 3.1.2 Released
The Maven team is pleased to announce the release of the Apache Maven EAR Plugin, version 3.1.0 This plugin generates a J2EE Enterprise Archive (EAR) file. https://maven.apache.org/plugins/maven-ear-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-ear-plugin 3.1.0 Release Notes - Apache Maven EAR Plugin - Version 3.1.0 Bug * [MEAR-285] EarMojo fails to handle assorted IO Errors * [MEAR-283] Not reproducible builds when skinnyWars option turned on * [MEAR-278] Ear plugin includes the same artifact twice if used without clean Improvement * [MEAR-279] make build Reproducible * [MEAR-194] Output during creation of Ear is not correct New Feature * [MEAR-280] Reproducible Builds: make entries in output ear files reproducible (order + timestamp) Task * [MEAR-284] Tests fail at HEAD on Linux * [MEAR-276] Upgrade maven-archiver to 3.4.0 Thank you to all contributors who helped to make this release. Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] dependabot[bot] opened a new pull request #203: Bump ant from 1.10.8 to 1.10.9
dependabot[bot] opened a new pull request #203: URL: https://github.com/apache/maven-site/pull/203 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
