dependabot[bot] commented on pull request #49:
URL:
https://github.com/apache/maven-artifact-transfer/pull/49#issuecomment-958970536
Superseded by #50.
--
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
dependabot[bot] closed pull request #49:
URL: https://github.com/apache/maven-artifact-transfer/pull/49
--
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,
dependabot[bot] commented on pull request #49:
URL:
https://github.com/apache/maven-artifact-transfer/pull/49#issuecomment-958970536
--
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
dependabot[bot] closed pull request #49:
URL: https://github.com/apache/maven-artifact-transfer/pull/49
--
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,
Usually you will endup with one engine and one or more test APIs.
The documentation above solves all combinations with junit4, junit5 and
testng.
If somebody uses one @Test annotation and wants to say that f/w1 should run
test class 1 but f/w2 should run test class 2, then the plugin should be
Hi Slawomir,
Pls follow this page
https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-platform.html
There is a chapter "How to run multiple APIs or Engines". There are also
some links pointing to our integration test in the Apache project.
Pls have a look.
Cheers
Tibor
On
Hi,
I understand the difference between framework and providers.
I also know that we can add specific providers as dependency to the plugin
and in the result we have manually selected providers.
When we don't configure any dependency the provider is chosen automatically
depending on what we
Hi Slawomir,
The reality is different.
It's not the frameworks but providers.
So the plugin iterates over providers.
You may choose whether you will define the provider artifacts in plugin
deps or you let the plugin to select the providers upon dependencies which
means that there is some logic
dependabot[bot] closed pull request #49:
URL: https://github.com/apache/maven-artifact-transfer/pull/49
--
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,
dependabot[bot] opened a new pull request #50:
URL: https://github.com/apache/maven-artifact-transfer/pull/50
Bumps [actions/checkout](https://github.com/actions/checkout) from 2.3.4 to
2.4.0.
Release notes
Sourced from
dependabot[bot] commented on pull request #49:
URL:
https://github.com/apache/maven-artifact-transfer/pull/49#issuecomment-958970536
Superseded by #50.
--
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
11 matches
Mail list logo
