Skip to content

Conversation

@rolnico
Copy link
Member

@rolnico rolnico commented Jan 8, 2026

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)
  • A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?
Relates to powsybl/powsybl-core#3443

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?

  • Yes
  • No

If yes, please check if the following requirements are fulfilled

  • The Breaking Change or Deprecated label has been added
  • The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

@rolnico rolnico self-assigned this Jan 8, 2026
@rolnico rolnico added the dependencies Pull requests that update a dependency file label Jan 8, 2026
Signed-off-by: Nicolas Rol <nicolas.rol@rte-france.com>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 8, 2026

@jeandemanged
Copy link
Member

How is the new file going to be maintained ? Shouldn't the license maven plugin be used instead to generate/update the file automatically on dependencies changes ?

@rolnico
Copy link
Member Author

rolnico commented Feb 2, 2026

How is the new file going to be maintained ? Shouldn't the license maven plugin be used instead to generate/update the file automatically on dependencies changes ?

This will be available once the PR powsybl/powsybl-parent#76 is merged in powsybl-parent. Feel free to test it and review it too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants