BOM / dependencies / project dependencies poms

[jonenst]

Describe the current behavior

if I override the version of powsybl-diagram from a powsybl-dependencies:

    <dependencyManagement>
        <dependencies>
            <!-- com.powsybl:powsybl-dependencies:2023.2.0 imports com.powsybl:powsybl-diagram:3.3.0, override to 4.0.0-SNAPSHOT before -->
            <dependency>
                <groupId>com.powsybl</groupId>
                <artifactId>powsybl-diagram</artifactId>
                <version>4.0.0-SNAPSHOT</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
            <dependency>
                <groupId>com.powsybl</groupId>
                <artifactId>powsybl-dependencies</artifactId>
                <version>2023.2.0</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

then iidm-impl gets scope test and programs crash at runtime:
com.powsybl.commons.PowsyblException: No NetworkFactoryService providers found

the com.powsybl:powsybl-diagram pom is supposed to be an easily importable "dependencies" pom by users (like https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-dependencies/3.1.2/spring-boot-dependencies-3.1.2.pom ) it shouldn't change the scopes of artifacts ? This has to do with separating poms for

• our own artifacts (BOMs)
• our runtime dependencies ("dependencies")
• the project build and test system (???)

Describe the expected behavior

import it and it doesn't break your app

Describe the motivation

simplicity. You can also workaround by restoring the scopes you want

Extra Information

it's always hard to do these things correctly with maven :(