Mixing Quarkus and Non-Quarkus Dependencies

[mbchangellc]

Is it generally safe to have both Quarkus and Non-Quarkus versions of a dependency in the same application. For example, we have a project that uses Spring Data JPA which declares a dependency on the non-Quarkus org.springframework.data:spring-data-jpa. We also use it in a Quarkus application which depends on io.quarkus:quarkus-spring-data-jpa. The non-Quarkus version is used in smaller applications that don't use Quarkus. My question is in general, providing a specific case here to clarify my question. I know we can declare the dependency with a scope that avoids it becoming a transitive dependency of other projects but would like to avoid repeating the dependencies everywhere it's used if possible. Thanks.