Bump core 6.0.1 #34

olperr1 · 2023-10-19T11:21:39Z

Please check if the PR fulfills these requirements

The commit message follows our guidelines
Tests for the changes have been added (for bug fixes / features)
Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem?

No

What kind of change does this PR introduce?

Dependency update

What is the current behavior?

powsybl-optimizer uses:

powsybl-core 5.3.2
powsybl-open-loadflow 1.2.1

What is the new behavior (if this is a feature change)?
powsybl-optimizer uses:

powsybl-core 6.0.1
powsybl-open-loadflow 1.3.0

Does this PR introduce a breaking change or deprecate an API?

The Breaking Change or Deprecated label has been added
The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

olperr1 · 2023-10-19T11:46:24Z

...reac/src/main/java/com/powsybl/openreac/parameters/output/network/AbstractNetworkOutput.java

-        List<String> lines = null;
-        try {
-            lines = Files.readAllLines(path);
-        } catch (IOException e) {


There is a little difference here.

Previously, no exception was thrown when an IOException was thrown during readAllLines .

Now, no exception is thrown when the file is not a regular file (real file + read access on it), but if another IOException is thrown, it will be propagated as an UncheckedIOException by the caller (see AmplModelExecutionHandler.readCustomFiles in powsybl-core). But I don't know if it can really happen.