[
https://issues.apache.org/jira/browse/SAMZA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072036#comment-14072036
]
Chris Riccomini commented on SAMZA-351:
---------------------------------------
Also, I was thinking of environment.gradle as a way to manipulate the project
AFTER it'd been setup. This is how we use it internally. If it goes first, it's
going to be impossible for us to predict how to reason about our open source
build.gradle since we'll never know what people are introducing into the
environment under the hood.
> Re-order environment.gradle apply
> ---------------------------------
>
> Key: SAMZA-351
> URL: https://issues.apache.org/jira/browse/SAMZA-351
> Project: Samza
> Issue Type: Bug
> Components: build
> Affects Versions: 0.7.0
> Reporter: Chris Riccomini
> Assignee: Chris Riccomini
> Fix For: 0.8.0
>
> Attachments: SAMZA-351-0.patch
>
>
> We apply environment.gradle before other plugins in build.gradle. This seems
> to be in the wrong order, since environment.gradle is meant to provide a way
> for people to override certain portions of the build.
> We use this internally to tweak certain plugins according to our needs, and
> we're seeing issues because we need to tweak plugins that are applied after
> environment.gradle.
> Simply moving the apply to the bottom of the list should fix this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
