[
https://issues.apache.org/jira/browse/IGNITE-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651503#comment-14651503
]
Yakov Zhdanov commented on IGNITE-1185:
---------------------------------------
Sergey, it seems that putting "classpath" before the path is an overhead.
Now this works as follows (process interrupted on any step on success):
# Check if URL is valid, if it is then use it.
# Check path relative to IGNITE_HOME
# Check if path is absolute
# Check classpath under META-INF
Let's alter the last point to check not only under META-INF. I think this will
be a solution.
> Locate configuration in class path
> ----------------------------------
>
> Key: IGNITE-1185
> URL: https://issues.apache.org/jira/browse/IGNITE-1185
> Project: Ignite
> Issue Type: Improvement
> Components: newbie
> Reporter: Yakov Zhdanov
> Assignee: Yakov Zhdanov
> Attachments: IGNITE-1185.patch
>
>
> Need ability to locate configuration in classpath, so nodes can be started
> like this:
> {{ignite.sh classpath:config/mycfg.xml}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
