aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sweeney (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-1357) Consider enabling requireExplicitBindings
Date Thu, 18 Jun 2015 21:47:00 GMT

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

Kevin Sweeney updated AURORA-1357:
----------------------------------
    Issue Type: Story  (was: Bug)

> Consider enabling requireExplicitBindings
> -----------------------------------------
>
>                 Key: AURORA-1357
>                 URL: https://issues.apache.org/jira/browse/AURORA-1357
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Kevin Sweeney
>
> Right now our Guice configuration allows the creation of JIT bindings, which makes it
hard to reason about which injector a provider will be created in. We should consider turning
up the [requireExplicitBindings|http://google.github.io/guice/api-docs/3.0/javadoc/com/google/inject/Binder.html#requireExplicitBindings()]
flag to avoid the pitfalls seen in https://reviews.apache.org/r/35627/.
> Since we've released 0.8.0 with a security SPI defined in terms of Guice Modules this
would be a backwards-incompatible change. We should introduce this change with a deprecation
warning message when implicit bindings are detected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message