You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gatling-gradle-plugin currently adds the mavenCentral repository if gatling is not found.
But my opinion is that it's not the purpose of such plugin to add it.
On the other hand, we should add an explaining message when gatling dependency is absent with the suggestion code to add mavenCentral (but let the user decide if they want to add another repository, such as proxy in enterprise environment).
The text was updated successfully, but these errors were encountered:
…tling#4259
Motivation:
Flaky tests and out of scope feature
Modifications:
* Remove automatic maven central configuration
* Display an explicit message when gatling dependencies are not reachable
Result:
Limit scope
Isammoc
added a commit
to gatling/gatling-gradle-plugin
that referenced
this issue
Jun 17, 2022
Motivation:
Flaky tests and out of scope feature
Modifications:
* Remove automatic maven central configuration
* Display an explicit message when gatling dependencies are not reachable
Result:
Limit scope
Closesgatling/gatling#4259
Motivation:
Flaky tests and out of scope feature
Modifications:
* Remove automatic maven central configuration
* Display an explicit message when gatling dependencies are not reachable
Result:
Limit scope
Closesgatling/gatling#4259
slandelle
changed the title
[Gradle] Remove maven central automatic configuration
Gradle: Remove maven central automatic configuration
Jun 20, 2022
slandelle
changed the title
Gradle: Remove maven central automatic configuration
Gradle: Remove maven central automatic configuration [BREAKING]
Jul 4, 2022
gatling-gradle-plugin currently adds the mavenCentral repository if gatling is not found.
But my opinion is that it's not the purpose of such plugin to add it.
On the other hand, we should add an explaining message when gatling dependency is absent with the suggestion code to add mavenCentral (but let the user decide if they want to add another repository, such as proxy in enterprise environment).
The text was updated successfully, but these errors were encountered: