Re: Maven conflicts within ignite-core from duplicated classes

We already have 2 dependencies at ignite-core: *javax.cache.cache-api* and *org.gridgain.ignite-shmem* (ASAIK we have an issue to redeploy org.gridgain.ignite-shmem as org.apache.ignite.ignite-shmem) On Thu, Jun 16, 2016 at 11:57 AM, Vladimir Ozerov wrote: > And why do we

Re: Maven conflicts within ignite-core from duplicated classes

And why do we afraid this dependency? It has "CLASS" retention so users do not need them in runtime, AFAIK. On Thu, Jun 16, 2016 at 11:19 AM, Vladislav Pyatkov wrote: > Why not just rename these classes? > > On Thu, Jun 16, 2016 at 11:16 AM, Semyon Boikov

Re: Maven conflicts within ignite-core from duplicated classes

Why not just rename these classes? On Thu, Jun 16, 2016 at 11:16 AM, Semyon Boikov wrote: > 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

Re: Maven conflicts within ignite-core from duplicated classes

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 wrote: > Hi Pete, > > CC-ing Ignite dev list to the thread as well. > > Igniters, up to today is there

Re: Maven conflicts within ignite-core from duplicated classes

Denis, I've created issue: https://issues.apache.org/jira/browse/IGNITE-3323 On Mon, Jun 13, 2016 at 10:04 AM, Denis Magda 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

Re: Maven conflicts within ignite-core from duplicated classes

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