> IMHO it should be the same for the entire camel-extra project. > And only the artifcatId should be changed for the various Maven modules.
Sounds fine. We can stick to the same groupId as in other Camel-Extra modules. And name artifact camel-example-esper . > Also IMHO dont make the artifactId long and dont repeat yourself. > And as the groupId have extra 2 times we may consider shorten that as well. > <groupId>org.apache-extras.camel</groupId> However somebody (Hadrian I suppose, as he migrated Camel-Extra to Apache Extras) already set groupId to org.apache-extras.camel-extra . Do you want to change groupId in entire project then? It's fine for me as org.apache-extras.camel sounds better, but I wanted to leave the existing groupId as approved by community. Summarizing: +1 for camel-example-esper as artifactId +1 for renaming groupId in whole camel-extra to org.apache-extras.camel +1 for using the same groupId for esper example Anybody wants to change anything in the three points above? -- Henryk Konsek http://henryk-konsek.blogspot.com
