Project definition in pom.xml contains wrong dependency definition (runtime)

[mariuszs]

sample project configuration:

<dependencies>
    ....
    <dependency>
        <groupId>com.ofg</groupId>
        <artifactId>micro-infra-spring</artifactId>
        <version>0.6.0</version>
    </dependency>
</dependencies>

mvn dependency:tree
[INFO] \- com.ofg:micro-infra-spring:jar:0.6.0:compile
[INFO]    +- com.ofg:micro-infra-spring-base:jar:0.6.0:runtime
[INFO]    |  +- org.aspectj:aspectjweaver:jar:1.8.4:runtime
[INFO]    |  +- com.ofg:micro-deps-spring-config:jar:0.4.8:runtime
[INFO]    |  |  +- com.ofg:micro-deps:jar:0.6.2:runtime
[INFO]    |  |  |  +- org.codehaus.groovy:groovy-all:jar:indy:2.3.7:runtime
[INFO]    |  |  |  +- org.apache.curator:curator-x-discovery:jar:2.6.0:runtime
[INFO]    |  |  |  |  +- org.apache.curator:curator-recipes:jar:2.6.0:runtime

As a result @EnableMicroservice cannot be used, only EnableAutoConfiguration is visible in project code. The only way to configure project is by component scan - all packaged are visible at runtime.

Sample project: https://github.com/mariuszs/micro-infra-spring-issues

[szpak]

That's a known limitation of maven-publish plugin. Peter recommends a workaround.