You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2016/01/02 20:27:39 UTC
[jira] [Commented] (BIGTOP-2170) Better organization of the gradle
build structure
[ https://issues.apache.org/jira/browse/BIGTOP-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076637#comment-15076637 ]
Konstantin Boudnik commented on BIGTOP-2170:
--------------------------------------------
True, you are [/kidding]
Well, yeah - names are getting a bit too long. I think it's a compromise between this inconvenience and running the risk of having same variables carrying different semantics in different places. Perhaps we can shorten namespaces?
> Better organization of the gradle build structure
> -------------------------------------------------
>
> Key: BIGTOP-2170
> URL: https://issues.apache.org/jira/browse/BIGTOP-2170
> Project: Bigtop
> Issue Type: Improvement
> Components: build
> Affects Versions: 1.0.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Fix For: 1.1.0
>
> Attachments: 0001-BIGTOP-2170.-Better-organization-of-the-gradle-build.patch, 0001-BIGTOP-2170.-Better-organization-of-the-gradle-build.patch
>
>
> With BIGTOP-2141, BIGTOP-2103, and others we are using more and more build and system properties. Over time, it is going to be more difficult to track them all either via the build or documentation. Hence, I propose to extract all user-controlled properties into {{build.properties}} which is designed exactly for this sort of things.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)