CODEWITHSUNDEEP
javaspringspring-bootmavenspring-data-jpa
Muhammad Hewedy
Muhammad Hewedy

Reputation: 30056

How to build a library around spring-boot that doesn't enforce a certain spring-boot version?

I am trying to build a library https://github.com/mhewedy/spring-data-jpa-mongodb-expressions on top of spring boot and spring Data JPA.

What I want to achieve and hence the library doesn't use explicitly implementation feature of spring boot or spring data JPA, I need to make this a library to take the version from the including project.

Currently, the version of spring boot is defined in the pom.xml

So, I think once I uploaded the jar to the maven repository, and whenever anybody depends on this jar, there might be a conflict in the spring dependencies (that comes from his project and what comes from this jar)

So my question is If I make the dependencies in pom.xml as Optional, do this will solve the problem? if not what other alternative solutions I can do?

EDIT:

Here's a list of types from spring I use in the library:

org.springframework.data.jpa.repository.JpaRepository;
org.springframework.data.repository.NoRepositoryBean;
org.springframework.data.domain.Page;
org.springframework.data.domain.Pageable;
org.springframework.data.domain.Sort;
org.springframework.data.jpa.domain.Specification;
org.springframework.data.jpa.repository.support.JpaEntityInformation;
org.springframework.data.jpa.repository.support.SimpleJpaRepository;

Upvotes: 0

Views: 321

Answers (1)

J Fabian Meier
J Fabian Meier

Reputation: 35805

For building your library, you need to use a given version of the dependencies. You need to choose one, otherwise the compiler cannot create a classpath and compile your code.

Somebody who uses your library might use another version of the dependencies. Their versions will (usually) override your versions because they win in the Maven dependency mediation. So your library will actually run with the versions that the library user specifies (if the library user does not use your dependencies, then your versions are still there).

So, the question that remains is: Will your code work with a newer/different version of the dependencies?

This cannot be said in general because it depends on the way the maintainer of the dependencies works.

Upvotes: 2

Related Questions