Hello.
I added a new property in Maven Deploy plugin called
retryFailedDeploymentDelay
This property impose a delay between 1 second to 5 minutes (max) between
retries. The intention is to make maven more solid and stable when network
glitches happens.
This pull request is: https://github.com/ap
Instead of using in Surefire (may affect the
ITs), there is a better trick.
See the POM surefire-junit47.
You will see the section of compiler endorsed classpath but Surefire has
different one:
maven-dependency-plugin
main
process-sources
copy
>>Or do we want to even share the test projects and work with profiles in
the test project pom?
I mean this.
It pretty depends on what we are going to test, either:
+ features of surefire-junit5 provider, or
+ features of junit5 itself.
I would say the provider in the first phase, and in the sec
Hi,
I've written a page[1] about the problem related to projects which need to
be compatible with pre Java9 versions, but also want to provide a
module-info file in case it is used in a Java 9 project. This is mainly an
issue for library builders, end-application builders can simply push
Hello Tibor,
Tibor Digana schrieb am Di., 4. Okt. 2016 um
02:29 Uhr:
> Can you simplify and speed up writing integration tests in the way that you
> would parameterize the existing JUnit 4 testing by adding Maven profiles
> (one default profile and junit5 profile) having another dependencies and
Hello Tibor,
Tibor Digana schrieb am Di., 4. Okt. 2016 um
02:14 Uhr:
> +1 to adopt JUnit 5 provider to Maven Surefire git branch.
> You would have to extend AbstractSurefireMojo.java with JUnit 5 provider in
> classpath builder.
>
I see, we would have to implement a ProviderInfo for JUnit 5. I
Github user britter commented on a diff in the pull request:
https://github.com/apache/maven-surefire/pull/125#discussion_r81810117
--- Diff:
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/JUnit47ConcurrencyIT.java
---
@@ -32,14 +32,14 @@
*
* @a