Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <BC340958-990B-4027-BB17-F87794782846@gridgain.com>
References: <CACxYLAzVhu8vCLLi1OsqRtc7CnxaGUvewoBhwSv=ZvE_Q2rCTA@mail.gmail.com>
 <BC340958-990B-4027-BB17-F87794782846@gridgain.com>
From: Semyon Boikov <sboikov@gridgain.com>
Date: Thu, 16 Jun 2016 11:16:21 +0300
Message-ID: <CAFx+i-a_dSQTYZtXmNd_q+N+yy0XJ4K3xxwOUj1hJbZ-pBDUsA@mail.gmail.com>
Subject: Re: Maven conflicts within ignite-core from duplicated classes
To: user@ignite.apache.org
Cc: Pete Campton <p.campton@qriously.com>, dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a1147410e786c9d053560daff
archived-at: Thu, 16 Jun 2016 08:16:32 -0000

--001a1147410e786c9d053560daff
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

As far as I know the only reason sources of Nullable are in Ignite - we did
not want to have any dependecy for 'core' module.

On Mon, Jun 13, 2016 at 10:04 AM, Denis Magda <dmagda@gridgain.com> wrote:

> 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=E2=80=99s annotation in Ignite sources?
>
> As I see we can rather import that latest version from the maven reposito=
ry
> 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.
>
> =E2=80=94
> Denis
>
> 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 confli=
ct
> 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, ElementType.TYPE_USE})
>
> 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 acros=
s
> a way of avoiding these conflicts?
>
> Thanks
> Pete
>
>
>

--001a1147410e786c9d053560daff--