Hi,
thank you for looking into this.
Ss shade plugin uses
<transformer
implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>
the services from all jars are merged into fat jar. It must be
something else. The application itself didn't change, only the camel
version
Am Mi., 29. Jan. 2020 um 14:52 Uhr schrieb Claus Ibsen-2 [via Camel]
<[email protected]>:
>
> Hi
>
> See this FAQ
> https://camel.apache.org/manual/latest/faq/how-do-i-use-a-big-uber-jar.html
>
> uber-jar self made are on your own. And it's a hazzle to do. The JARs
> have files in META-INF/services which you need to ensure all of them
> gets shaded, and whatelse.
>
>
> On Wed, Jan 29, 2020 at 2:19 PM Dennis Holunder <[hidden email]> wrote:
>
> >
> > Hello,
> >
> > I've migrated an app to camel 3 which works fine in IDE, but starting
> > fat jar produces the errors like: java.lang.NoClassDefFoundError:
> > com/lmax/disruptor/EventTranslatorVararg. The approach works with
> > camel 2.22 version
> >
> > I'm using latest weld-se-shaded, deltaspike-cdictrl-weld and
> > maven-shade-plugin.
> >
> > Any hints why it is not working in camel-3? I've attached sample project
> >
> > Thanks!
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> https://camel.465427.n5.nabble.com/Camel-3-0-1-standalone-main-cdi-fat-jar-not-working-tp5854380p5854388.html
> To unsubscribe from Camel, click here.
> NAML
