[
https://issues.apache.org/jira/browse/IGNITE-12765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130412#comment-17130412
]
Aleksey Plekhanov commented on IGNITE-12765:
--------------------------------------------
[~ilyak], of course, I have no objections to slim release as part of 2.9
I've had a brief look at PR. My comments:
* I think we should somehow describe the ability to build slim releases for
developers (at least in DEVNOTES.txt) as part of this PR.
* We already moved some artifacts to ignite extensions (ignite-flink,
ignite-flume, ignite-twitter, ignite-zeromq, etc). Do we really need to exclude
these artifacts in assembly XML?
* Shouldn't we mention in README.txt type of release and difference between
slim and full release?
* There are still javadocs for excluded artifacts exist in a slim release. Do
we really need them? Can we exclude it too?
* Examples also include some code which uses excluded artifacts (ml and spark
for example)
> Slim binary release and docker image for Apache Ignite
> ------------------------------------------------------
>
> Key: IGNITE-12765
> URL: https://issues.apache.org/jira/browse/IGNITE-12765
> Project: Ignite
> Issue Type: Task
> Reporter: Maxim Muzafarov
> Assignee: Ilya Kasnacheev
> Priority: Blocker
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 1. Prepare Apache Ignite "slim" distribution (example:
> https://github.com/apache/ignite/tree/ignite-slim)
> 2. Update configuration and check Apache Ignite RELEASE TeamCity Suite
> according to a new additional package distribution.
> See - discussion on dev-list
> http://apache-ignite-developers.2346864.n4.nabble.com/Slim-binary-release-and-docker-image-for-Apache-Ignite-td45110.html
> {code}
> libs:
> core/shmem/jcache
> ignite-indexing
> ignite-spring
> libs/optional:
> ignite-compress
> ignite-rest-http
> ignite-spring-data_2.2
> ignite-log4j2
> ignite-log4j
> ignite-slf4j
> ignite-opencensus
> ignite-kubernetes
> ignite-urideploy
> ignite-jta
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
