You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2022/04/13 12:57:00 UTC

[jira] [Updated] (IGNITE-16815) [Extensions] Ignite extensions must use ignite-parent as a parent project

     [ https://issues.apache.org/jira/browse/IGNITE-16815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Muzafarov updated IGNITE-16815:
-------------------------------------
    Ignite Flags:   (was: Docs Required,Release Notes Required)

> [Extensions] Ignite extensions must use ignite-parent as a parent project
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-16815
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16815
>             Project: Ignite
>          Issue Type: Improvement
>          Components: extensions
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Major
>             Fix For: 2.14
>
>
> Ignite Extensions currently use their own maven parent project which is lead for duplicated configuration of maven profiles, dependency versions and the build lifecycle. Since the ignite-parent pom is now available it's better to use shared pom as single parent for all extensions.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)