ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@gridgain.com>
Subject Re: Maven conflicts within ignite-core from duplicated classes
Date Mon, 13 Jun 2016 07:04:05 GMT
Hi Pete,

CC-ing Ignite dev list to the thread as well.

Igniters, up to today is there any reason why we need to include sources of Nullable JetBrain’s
annotation in Ignite sources?

As I see we can rather import that latest version from the maven repository
https://maven-repository.com/artifact/org.jetbrains/annotations/15.0 <https://maven-repository.com/artifact/org.jetbrains/annotations/15.0>

Anton, please take a look at Pete issue and suggest a workaround and generic solution overall.


> On Jun 9, 2016, at 1:32 PM, Pete Campton <p.campton@qriously.com> wrote:
> Hello,
> I've come across an issue where there are a couple of classes duplicated from org.jetbrains.annotations
within the ignite-core module which conflict with other part of our code base.
> As these files are duplicated rather than being referenced as a maven dependency I am
unable to exclude them or reference a specific version of the org.jetbrains.annotations artifact.
> Specifically, the included version cannot be used to annotate types
> ignite-core-1.6.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER, ElementType.LOCAL_VARIABLE})
> annotations-15.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER, ElementType.LOCAL_VARIABLE,
> As far as I know there isn't an easy way of excluding these files from within the ignite-core
module. Is there are reason why these "external" files have been duplicated within the ignite
code base rather than being referenced as a maven dependency? Or alternatively, has anyone
come across a way of avoiding these conflicts?
> Thanks
> Pete

View raw message