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

XML

Word

Printable

JSON

Details

Type: Task
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.13
Component/s: extensions
Labels:
None

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.

Attachments

Issue Links

is part of

IGNITE-16855 [Umbrella] Apache Ignite Extension Release Process

Resolved

is related to

IGNITE-16852 Ignite compatibility framework can exclude unnecessary jars from test java process classpath

Resolved

IGNITE-16592 Add ignite-parent pom and bom to a release lifecycle

Resolved

links to

GitHub Pull Request #110

GitHub PullRequest: 110

Activity

People

Assignee:: Maxim Muzafarov

Reporter:: Maxim Muzafarov

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 07/Apr/22 12:14

Updated:: 21/Apr/22 10:38

Resolved:: 21/Apr/22 10:38

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

20m