Hi, It sounds good to me.
Regards JB > Le 28 mai 2020 à 17:18, Omar Al-Safi <[email protected]> a écrit : > > Hi Claus, > > Thanks for clarifying. Then that was some confusion from my side. > Sure, I guess we can proceed with `camel-component-maven-plugin` naming. > > Regards, > Omar > > On Thu, May 28, 2020 at 4:21 PM Claus Ibsen <[email protected]> wrote: > >> Hi >> >> The existing camel-maven-plugin is for running Camel with the run goal. >> It's for Camel end user applications. >> >> The ticket you work on is for Camel component or data format >> developers, and not for end user applications. >> >> It should basically just be a single goal that takes the relevant >> existing goals from the camel-package-maven-plugin >> and execute them in the right order. >> >> We have almost that today. >> >> https://github.com/apache/camel/blob/master/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/GenerateComponentMojo.java >> >> But being a new plugin with a single goal, then its easier for end >> users as there are not 25 other "internal goals for Camel project" >> that gets in your way. >> And we should then also document this new plugin and its goal. And >> update the maven archetypes to use this plugin. >> >> About the name, then there is a clash. >> >> We could name it >> >> camel-component-maven-plugin >> >> >> On Thu, May 28, 2020 at 3:38 PM Omar Al-Safi <[email protected]> wrote: >>> >>> Hello Camelers, >>> >>> I just started working on creating a maven plugin for end-users to >> generate >>> configurations, DSLs .. etc based on the camel-package-maven-plugin. >>> Now I have the first world problem to name the plugin, personally, I am >>> thinking of this naming `*camel-maven-plugin*`, is simple and I think it >>> serves the purpose for the users. Hence when the user execute the plugin >>> for example, will be something like this: >>> `*mvn >> org.apache.camel:camel-maven-plugin:<version>:generate-configuration* >>> `. >>> However, as I can see here >>> < >> https://github.com/apache/camel/tree/master/tooling/maven/camel-maven-plugin >>> >>> there is already another plugin `camel-maven-plugin` with one MOJO, I am >>> not sure if this should be internal or can be used by the users. If this >>> plugin serves a different purpose, I was thinking to name it to something >>> else and reserve `camel-maven-plugin` naming for end-users. Any thoughts? >>> >>> Regards, >>> Omar >> >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >>
