You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2021/10/29 16:25:00 UTC
[jira] [Created] (IGNITE-15850) Ignite build fails on Maven of
recent versions
Roman Puchkovskiy created IGNITE-15850:
------------------------------------------
Summary: Ignite build fails on Maven of recent versions
Key: IGNITE-15850
URL: https://issues.apache.org/jira/browse/IGNITE-15850
Project: Ignite
Issue Type: Bug
Components: build
Affects Versions: 2.13
Reporter: Roman Puchkovskiy
Assignee: Roman Puchkovskiy
Namely, build fails on Maven 3.8.3. This happens because since some version Maven started blocking plain http (not https) repositories.
We still mention our own GridGain repository using plain http:// link, and it can be fixed easily.
But there is another problem: jotm-core:2.2.3 uses jotm:2.2.3 as parent, which in turn uses ow2:1.3 as parent. ow2:1.3 mentions its own http:// repository in <repository> element, also it mentions its http:// repositories via properties:
{{<ow2DistMgmtSnapshotsUrl>http://repository.ow2.org/nexus/content/repositories/snapshots</ow2DistMgmtSnapshotsUrl>
<ow2DistMgmtReleasesUrl>http://repository.ow2.org/nexus/service/local/staging/deploy/maven2</ow2DistMgmtReleasesUrl>}}
Probably it's just enough to override these properties in our parent pom.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)