[ https://issues.apache.org/jira/browse/IGNITE-12765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098911#comment-17098911 ]
Maxim Muzafarov commented on IGNITE-12765: ------------------------------------------ [~ilyak] AFAIK, currently, we are using the following command to prepare the Apache Ignite release package: {code} -Prelease,all-scala -Dignite.edition=apache-ignite {code} If we will wish to assembly `full` and `slim` package per single command (e.g. full release prepare) it's impossible to achieve with this command. Right? Should we consider having {{-Dignite.editions}} environment variable for this case or we should build assemblies one by one? > 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)