Hi This is not a chicken and egg problem. I've recreated a basic project illustrating the problem
git clone https://bitbucket.org/minh_tran__/camel_plugin_bug.git mvn clean test. -> will always fail. I've ensured clean will always remove the autogenerated classes mvn test -> second attempt without the clean will pass On Mon, 28 Mar 2022 at 19:32, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > Its a chicken and egg situation. Therefore its best to use the plugin > to generate the source code ahead of time, eg in src/generated or > directly into the source folder - as shown in the doc page. > > On Mon, Mar 28, 2022 at 10:24 AM Minh Tran <minh.tran...@gmail.com> wrote: > > > > On Mon, 28 Mar 2022 at 18:14, Claus Ibsen <claus.ib...@gmail.com> wrote: > > > > > Hi > > > > > > The docs tells you where it outputs and how you can add plugins to > > > include the src/generated folder > > > > https://camel.apache.org/manual/camel-component-maven-plugin.html#_generate > > > > > > Yes you can change the defaults but the problem is that the current > > defaults help to hide the bug in the plugin. > > > > > > > > > > You can also set which phase to execute the plugin > > > > > > > I tried both generated-sources and compile phase. > > - generated-sources didn't generate anything. > > - compile did generate the code but it executes after the compiler runs > so > > it never gets a chance to compile it. I tried moving the > > camel-component-maven-plugin to appear before the maven-compiler-plugin > in > > the pom.xml but this seems to have no effect in the order of execution. I > > am using maven 3.6.0 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
