Well I just read the migration guide and thought the use of the “modular” approach was to end up with a smaller build including ONLY those I specifically included.
> Maven users of Apache Camel can keep using the dependency camel-core which > has transitive dependencies on all of its modules, and therefore no migration > is needed. However, users who want to trim the size of the classes on the > classpath, can use fine grained Maven dependencies on only the modules > needed. You may find how to do that in the examples. M > On 18 Feb 2020, at 15:33, Giovanni Condello } <[email protected]> wrote: > > Hi Mikael, > > You can technically exclude any dependencies you want via maven <exclusions> > but.... to be honest I don't see the point and you may end up creating more > issues for users of your library (?). > > camel-core, camel-main are there because they are compile-time deps of e.g. > camel-sql > > Can you explain a little bit more the rationale behind this request? > > Cheers > Giovanni > > -----Messaggio originale----- > Da: Mikael Andersson Wigander <mikael.grevsten@'mail.com> > Inviato: martedì 18 febbraio 2020 15:27 > A: [email protected] > Oggetto: Camel 3 pom for JVM 1.8 > > Hi > > My pom includes a dependencyManagement statement for camel (3.0.1) > > <dependency> > <groupId>org.apache.camel.springboot</groupId> > <artifactId>camel-spring-boot-dependencies</artifactId> > <version>${camel.version}</version> > <type>pom</type> > <scope>import</scope> > </dependency> > and then these dependencies > > <dependency> > <groupId>org.apache.camel.springboot</groupId> > <artifactId>camel-quartz-starter</artifactId> > </dependency> > <dependency> > <groupId>org.apache.camel.springboot</groupId> > <artifactId>camel-sql-starter</artifactId> > </dependency> > <dependency> > <groupId>org.apache.camel.springboot</groupId> > <artifactId>camel-activemq-starter</artifactId> > </dependency> > <dependency> > <groupId>org.apache.camel.springboot</groupId> > <artifactId>camel-direct-starter</artifactId> > </dependency> > <dependency> > <groupId>org.apache.camel.springboot</groupId> > <artifactId>camel-bean-starter</artifactId> > </dependency> > > but in my build I see several camel dependencies included in the war file > that I haven’t specified, esp. camel-core, camel-main… The ones included are > stated here: > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_modularization_of_camel_core > > How can I make it more modular and only include dependencies I have stated? > > > M >
