[MNG-7667] Fix DownloadMojo to properly resolve (#236)

The m-p-p depends on m-p-tools-ant and m-p-tools-beanshell as runtime/optional, and the way DownloadMojo resolves every artifact causes that OptionalDependencySelector filter these out even at "collection" stage (as depth >= 2).

Hence, fix DownloadMojo to resolve properly, that actually shifts all the tree "one level up", and hence result is same as in Maven, as the optional dependencies become "first level sibling".

---

https://issues.apache.org/jira/browse/MNG-7667
1 file changed
tree: aa91ad95234c94c5d80e730119d33d38e7f0c4a6
  1. .github/
  2. core-it-suite/
  3. core-it-support/
  4. environments/
  5. src/
  6. .asf.yaml
  7. .gitattributes
  8. .gitignore
  9. Jenkinsfile
  10. pom.xml
  11. README.md
  12. run-its.bat
  13. run-its.sh
README.md

Maven Core Integration Tests

https://maven.apache.org/core-its/

If you want to run the integration tests against a custom build of Maven use the following command:

mvn clean install -Prun-its -Dmaven.repo.local=`pwd`/repo -DmavenDistro=/path/to/apache-maven-dist.zip

or if behind a proxy

mvn clean install -Prun-its -Dmaven.repo.local=`pwd`/repo -DmavenDistro=/path/to/apache-maven-dist.zip -Dproxy.active=true -Dproxy.type=http -Dproxy.host=... -Dproxy.port=... -Dproxy.user=... -Dproxy.pass=...

Using the script

Build Maven core with the profile -PversionlessMavenDist

Now Run the script: sh ./run-its.sh

Maven Developers List: dev@maven.apache.org