FWIW, I ran maven integration tests (commit 73a2b7) against current
maven master and got this
> Tests run: 771, Failures: 3, Errors: 21, Skipped: 0
Running the same test checkout with Maven 3.3.9
> Tests run: 771, Failures: 0, Errors: 0, Skipped: 0
--
Regards,
Igor
On Wed, Nov 16, 2016, at
So have you not asked, after committing changes, if something should not be
rolled back? If you can take the integration tests from the commit right after
the 3.3.9 release and Maven master works against that I’ll be perfectly
satisfied that we will not be breaking the user base.
> On Nov 15,
GitHub user trajano opened a pull request:
https://github.com/apache/maven/pull/97
.travis and SonarQube.com support
This PR provides two commits, the first one adds Travis build support.
https://travis-ci.org/trajano/maven
The second adds SonarQube support. For the
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/112
@cardil
`-DrunOrder=random:123456` I meant as well.
The enums are only some model representation of real world but it does not
mean that we cannot change it.
What we should not
