You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2020/06/29 11:24:00 UTC

[jira] [Updated] (IGNITE-13195) Allow skipping autotools invocation when building Ignite release

     [ https://issues.apache.org/jira/browse/IGNITE-13195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ilya Kasnacheev updated IGNITE-13195:
-------------------------------------
    Ignite Flags:   (was: Release Notes Required)

> Allow skipping autotools invocation when building Ignite release
> ----------------------------------------------------------------
>
>                 Key: IGNITE-13195
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13195
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Goncharuk
>            Priority: Major
>
> I do not have an up-to-date set of autotools installed on local machine, and Apache Ignite release build fails locally with the following error:
> {code}
> main::scan_file() called too early to check prototype at /usr/local/bin/aclocal line 617.
> configure.ac:36: warning: macro `AM_PROG_AR' not found in library
> configure.ac:21: error: Autoconf version 2.69 or higher is required
> configure.ac:21: the top level
> autom4te: /usr/bin/m4 failed with exit status: 63
> aclocal: autom4te failed with exit status: 63
> {code}
> I do not need to run these commands locally because I only need a quick assembly (java only, even no javadocs) to verify the release structure and command-line utilities integrity.
> It would be great to move these commands to a separate profile (enabled by default) so users can skip them when building the release package, something like {{mvn initialize -Prelease -P!autotools}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)