You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2021/08/13 13:33:00 UTC
[jira] [Updated] (IGNITE-15304) Validate POM files for duplicate
dependencies
[ https://issues.apache.org/jira/browse/IGNITE-15304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Mashenkov updated IGNITE-15304:
--------------------------------------
Component/s: build
> Validate POM files for duplicate dependencies
> ---------------------------------------------
>
> Key: IGNITE-15304
> URL: https://issues.apache.org/jira/browse/IGNITE-15304
> Project: Ignite
> Issue Type: Bug
> Components: build
> Reporter: Semyon Danilov
> Assignee: Peter Ivanov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> Some problems were encountered while building the effective model for org.apache.ignite:ignite-raft:jar:3.0.0-SNAPSHOT
> 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.ignite:ignite-core:test-jar -> duplicate declaration of version (?) @ line 119, column 21
> It is highly recommended to fix these problems because they threaten the stability of your build.
> For this reason, future Maven versions might no longer support building such malformed projects.{code}
> It seems that we've encountered duplicate dependency declarations. Such misconfiguration threatens the stability of a build, so it should be eliminated before the merge. I propose adding dependency:analyze-duplicate to the sanity checks phase
--
This message was sent by Atlassian Jira
(v8.3.4#803005)