You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/11/30 12:38:00 UTC

[jira] [Commented] (CAMEL-18765) Extend PrepareParentPomMojo to automatically generate/replace catalog/core and other sections

    [ https://issues.apache.org/jira/browse/CAMEL-18765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641275#comment-17641275 ] 

Claus Ibsen commented on CAMEL-18765:
-------------------------------------

Tom as Camel v3 is slowing down as we will shift focus for Camel v4 then lets avoid too many more changes. When we have a more stable v4 then we can look at this for that version

> Extend PrepareParentPomMojo to automatically generate/replace catalog/core and other sections
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-18765
>                 URL: https://issues.apache.org/jira/browse/CAMEL-18765
>             Project: Camel
>          Issue Type: Task
>          Components: build system
>    Affects Versions: 3.20.0
>            Reporter: Thomas Cunningham
>            Assignee: Thomas Cunningham
>            Priority: Major
>
> At the moment, PrepareParentPomMojo only generates the components section of the parent/pom.xml : 
> [https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/PrepareParentPomMojo.java#L73-L76]
> This could easily be extended so that the catalog and the core sections (and possibly others) could also be generated, which would keep the parent pom in sync with the camel code base.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)