-
Notifications
You must be signed in to change notification settings - Fork 1
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
Database iidm update for fictitiousP0 and Q0 #55
Conversation
Signed-off-by: David BRAQUART <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally, you can remove the overrided empty method testSetterGetter in BusBreakerIT tck test class ...
pom.xml
Outdated
@@ -50,7 +50,7 @@ | |||
<properties> | |||
<sirocco.version>1.0</sirocco.version> | |||
|
|||
<powsybl-ws-dependencies.version>2.12.0</powsybl-ws-dependencies.version> | |||
<powsybl-ws-dependencies.version>2.13.0-SNAPSHOT</powsybl-ws-dependencies.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use only release version in pom.xml ...
Wait for PR : powsybl/powsybl-network-store#430 to be merged and a new release of powsybl-network-store client to be created, and then override the negwork-store client version in the pom.xml ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes!
Signed-off-by: David BRAQUART <[email protected]>
# Conflicts: # pom.xml
# Conflicts: # network-store-server/src/main/resources/db/changelog/db.changelog-master.yaml
Quality Gate passedIssues Measures |
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: