You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2021/06/16 15:39:00 UTC
[jira] [Updated] (IGNITE-14917) Fix internal packages naming in
configuration modules
[ https://issues.apache.org/jira/browse/IGNITE-14917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Bessonov updated IGNITE-14917:
-----------------------------------
Description:
{{org.apache.ignite.internal.}} should be a continuous prefix.
Current packages ...configuration.internal.* and ...configuration.processor.internal.* break this rule. There's also package collision in configuration module that can be avoided.
was:{{org.apache.ignite.internal.}} should be a continuous prefix.
> Fix internal packages naming in configuration modules
> -----------------------------------------------------
>
> Key: IGNITE-14917
> URL: https://issues.apache.org/jira/browse/IGNITE-14917
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha2
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> {{org.apache.ignite.internal.}} should be a continuous prefix.
> Current packages ...configuration.internal.* and ...configuration.processor.internal.* break this rule. There's also package collision in configuration module that can be avoided.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)