[IGNITE-16815] [Extensions] Ignite extensions must use ignite-parent as a parent project

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.13
• Component/s: extensions
• Assignee: Maxim Muzafarov
• Reporter: Maxim Muzafarov
• Created: 07/Apr/22 12:14
• Updated: 21/Apr/22 10:38
• Resolved: 21/Apr/22 10:38

Description

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.

Issue Links

• is part of: IGNITE-16855 [Umbrella] Apache Ignite Extension Release Process
• is related to: IGNITE-16852 Ignite compatibility framework can exclude unnecessary jars from test java process classpath
• is related to: IGNITE-16592 Add ignite-parent pom and bom to a release lifecycle
• links to: GitHub Pull Request #110
• links to: GitHub PullRequest: 110