[
https://issues.apache.org/jira/browse/IGNITE-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395204#comment-15395204
]
Anton Vinogradov commented on IGNITE-3323:
------------------------------------------
Fixed, thanks for tip.
> Get rid of copypasted JB annotations, use dependency instead.
> -------------------------------------------------------------
>
> Key: IGNITE-3323
> URL: https://issues.apache.org/jira/browse/IGNITE-3323
> Project: Ignite
> Issue Type: Task
> Affects Versions: 1.5.0.final
> Reporter: Anton Vinogradov
> Assignee: Anton Vinogradov
> Priority: Minor
> Labels: newbie
> Fix For: 1.7
>
>
> From user request:
> {quote}
> 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, 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 across a way of avoiding
> these conflicts?
> {quote}
> Seems we have to remove these classes from Ignite code and use maven
> dependency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
