[
https://issues.apache.org/jira/browse/IGNITE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643550#comment-14643550
]
Konstantin Boudnik commented on IGNITE-1160:
--------------------------------------------
To add to the discussion going on the list and particularly to [~agoncharuk]
idea: the artifacts could be pulled from any repo-server using gradle's API and
the URI can be simply added to the configuration in the standard form
{code}org.hibernate:hibernate-core:3.6.7.Final{code} (or [more
from|https://docs.gradle.org/current/userguide/artifact_dependencies_tutorial.html]).
Adding such functionality to Ignite with Gradle APIs would be darn simple, I
reckon.
I personally would refrain from covering cases like 'building artifacts from
Mercurial/Git/SVN using gradle/ant' simply because in a sane engineering
environment the artifacts would be managed in some form or repo and not laying
around in a pile.
> Ignite.deploy(...) method to automatically deploy user code and libraries
> -------------------------------------------------------------------------
>
> Key: IGNITE-1160
> URL: https://issues.apache.org/jira/browse/IGNITE-1160
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Reporter: Dmitriy Setrakyan
> Fix For: sprint-9
>
>
> Implement {{Ignite.deploy(...}} method to automatically deploy user code and
> libraries on all Ignite server nodes.
> The method should accept the following parameters:
> # A collection of URIs to get user archives from (ZIPs and JARs should be
> handled.
> # A collection of GIT repositories with a POM file
> # A collection of Maven artifacts and Maven repositories.
> We should also add {{-deploy}} option to the {{ignite.sh}} script should
> should start a client node and automatically deploy the specified artifacts
> (supporting all the options listed above)
> The process should be as follows:
> # start as many server nodes as needed.
> # start a client node, call {{deploy(...)}} and then start using the client.
> # alternatively, call {{ignite.sh -deploy}} to deploy code on the servers,
> before starting using Ignite.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
