Which spring jars do i need

Component will be loaded, added to the Camel context and run. Edit this Page. Making sure Camel context is running in standalone Spring Boot To ensure the Spring Boot application keeps running until being stopped or the JVM terminated, typically only need when running Spring Boot standalone, i. Spring Boot configuration support Each component starter lists configuration parameters you can configure in the standard application.

Adding Camel routes Camel routes are detected in the Spring application context, for example a route annotated with org. RouteBuilder; import org. It is possible that some of the transitive dependencies may be unused, but there is no automated way to determine this. Some of them would fail compilation, others fail app at runtime. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. What are the minimum jars needed for spring to be used in a standalone application? Ask Question. Asked 9 years, 10 months ago. Active 7 years, 6 months ago. Viewed 12k times. Improve this question. Since you're using Maven, why don't you list only your direct dependencies, and let Maven download the transitive dependencies for you? This will help users to understand what they are and when and how to use them.

It also explains why exclusions are made on a per dependency basis instead of at the POM level. Optional dependencies are used when it's not possible for whatever reason to split a project into sub-modules.

The idea is that some of the dependencies are only used for certain features in the project and will not be needed if that feature isn't used. Ideally, such a feature would be split into a sub-module that depends on the core functionality project. This new subproject would have only non-optional dependencies, since you'd need them all if you decided to use the subproject's functionality.

However, since the project cannot be split up again, for whatever reason , these dependencies are declared optional. If a user wants to use functionality related to an optional dependency, they have to redeclare that optional dependency in their own project. This is not the clearest way to handle this situation, but both optional dependencies and dependency exclusions are stop-gap solutions.

Optional dependencies save space and memory. They prevent problematic jars that violate a license agreement or cause classpath issues from being bundled into a WAR, EAR, fat jar, or the like. The diagram above says that Project-A depends on Project-B. It's just like a normal build where Project-B will be added in Project-A's classpath. Project-B is not included in the classpath of Project-X. Suppose there is a project named X2 that has similar functionality to Hibernate.

Each supported database requires an additional dependency on a driver jar.