[ 
https://issues.apache.org/jira/browse/IGNITE-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132129#comment-15132129
 ] 

ASF GitHub Bot commented on IGNITE-2451:
----------------------------------------

GitHub user Dmitriyff opened a pull request:

    https://github.com/apache/ignite/pull/457

    IGNITE-2451 remove xml and java data render from controller

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Dmitriyff/ignite ignite-2451

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/457.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 #457
    
----
commit 9037007067d3fbb9f4625f9ddc64ebf4d9c8ef46
Author: Dmitriyff <[email protected]>
Date:   2016-01-27T09:40:02Z

    IGNTIE-2451 refactoring output data section

commit e750159932a0f6b84bf11f96ceeb2ef31e03d6be
Author: Dmitriyff <[email protected]>
Date:   2016-02-04T02:44:17Z

    Merge branch 'ignite-843-rc2' into ignite-2451

commit 8771fbdfabc91680300670567fa358558682bdad
Author: Dmitriyff <[email protected]>
Date:   2016-02-04T10:39:16Z

    IGNITE-2451 remove xml and java data render from controller

commit 2720bc82752ef42b30524910c86936f70defae31
Author: Dmitriyff <[email protected]>
Date:   2016-02-04T10:40:19Z

    Merge branch 'ignite-843-rc2' of 
https://git-wip-us.apache.org/repos/asf/ignite into ignite-2451

----


> Optimize code generator after change data on cluster page 
> ----------------------------------------------------------
>
>                 Key: IGNITE-2451
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2451
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: wizards
>            Reporter: Dmitriyff
>            Assignee: Dmitriyff
>             Fix For: 1.7
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to