[
https://issues.apache.org/jira/browse/IGNITE-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270691#comment-16270691
]
Dmitriy Pavlov commented on IGNITE-7070:
----------------------------------------
[~agoncharuk], could you please review my changes in PR
https://github.com/apache/ignite/pull/3106
https://ci.ignite.apache.org/viewQueued.html?itemId=969136&tab=queuedBuildOverviewTab
> Ignite PDS compatibilty framework: implement configurable classpath, JVM
> options, node startup timeout
> ------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-7070
> URL: https://issues.apache.org/jira/browse/IGNITE-7070
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Dmitriy Pavlov
> Assignee: Dmitriy Pavlov
> Priority: Critical
> Fix For: 2.4
>
>
> Ignite PDS compatibilty framework filters out classpath from current test
> classpath.
> It involves only ignite-core and there is no warning about it in pom.xml
> During extending scope of testing it is requied to extend CP with
> ignite-indexing, spring etc.
> It is required to add ability to configure filtered out classpath element by
> test.
> Additional fixes:
> - dump classpath in case multi-jvm mode startup failed
> - dump classpath in case multi-jvm mode startup hangs
> - make node join timeout configurable (post startup may require considerable
> amount of time
> - wait detached node not in assert (assert with side effect)
> Fixes are prepared in
> https://github.com/apache/ignite/pull/3106
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
