You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/07 11:49:00 UTC
[jira] [Commented] (IGNITE-7538) Introduce new test project for
Ignite 2.0+ with Java 8 / Java 9 compatibility
[ https://issues.apache.org/jira/browse/IGNITE-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355351#comment-16355351 ]
ASF GitHub Bot commented on IGNITE-7538:
----------------------------------------
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3482
IGNITE-7538 Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7538
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3482.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3482
----
commit f3b4e8bf9e65350d6c35b787e173f21d08794d79
Author: Ivanov Petr <pi...@...>
Date: 2018-02-06T08:22:23Z
IGNITE-7538 Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility
* updated versions of flatten-maven-plugin and apache-rat-plugin for RAT licenses check task
commit d72815bf86bbaf4bef53e8bba40d3beaf18611bb
Author: Ivanov Petr <pi...@...>
Date: 2018-02-07T11:44:20Z
IGNITE-7538 Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility
* update maven-javadoc-plugin version
----
> Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility
> -----------------------------------------------------------------------------
>
> Key: IGNITE-7538
> URL: https://issues.apache.org/jira/browse/IGNITE-7538
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Peter Ivanov
> Assignee: Peter Ivanov
> Priority: Critical
>
> After IGNITE-7203 and IGNITE-6730 there are two separate test project at CI which meet the problem of test configuration synchronization. It is necessary to devise a solution for overcoming this issue.
> Possible approaches:
> # Single project for tests with run with different parameters.
> Problems:
> #* Test History will show history for all builds with any parameters combination.
> #* Mute test will mute test for all parameters configuration.
> # Several project (differentiated by parameter) with build configuration synchronisation automation.
> Problems:
> #* Maintainability — how to seamlessly support build configuration synchronisation.
> Research for both approaches must be held.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)