Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed #246 Check maven-surefire-plugin configuration/definition #249

Conversation

khmarbaise
Copy link
Contributor

Removed provider dependencies, cause this will be done
by maven-surefire/maven-failsafe automatically.
Added maven-enforcer rule to make sure maven-surefire/
maven-failsafe/maven-surefire-report-plugin will have
the same version.

Removed provider dependencies, cause this will be done
by maven-surefire/maven-failsafe automatically.
Added maven-enforcer rule to make sure maven-surefire/
maven-failsafe/maven-surefire-report-plugin will have
the same version.
@obfischer
Copy link
Collaborator

Looks fine. Thx.

@obfischer
Copy link
Collaborator

Applied the patch manually (I hate merge commits).

@obfischer obfischer closed this Sep 19, 2015
@DirkMahler
Copy link
Member

There was a situation when we needed to specify the provider - as far as I remember the TestNG plugin contained classes with both JUnit and TestNG annotations. Just had a look the plugin module, the situation is no longer this way, thus it should be ok to simplify surefire configuration.

@obfischer
Copy link
Collaborator

It would be good to document the relationals behind this directly in the source or what ever. Every decision has a good reason but after sometime no ones remembers the reason.

@khmarbaise khmarbaise deleted the issue-246-check-surefire-configuration branch September 19, 2015 22:47
@obfischer
Copy link
Collaborator

See #249 for problems causes be this fix. Relates to #252

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants