GitHub user chtyim opened a pull request:

    https://github.com/apache/incubator-twill/pull/32

    (TWILL-69) Removed guava dependencies from twill-api and twill-common 
modules

    Following changes are backward incompatible:
    - TwillController no longer extends from Guava Service
      - No more start() method. stopAndWait() becomes terminate()
    - TwillRunnerService no longer extends from Guava Service
      - Only has the blocking start() and stop() for start and stop.
    - Classes moved from twill-common to twill-core, hence no long public
      - o.a.t.common.Services
      - o.a.t.common.ServiceListenerAdapter
      - o.a.t.common.CompositeService
      - o.a.t.common.DefaultResourceReport
    
    Modified all unit-tests and examples to use the new API

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chtyim/incubator-twill feature/TWILL-69

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-twill/pull/32.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #32
    
----
commit 0d217b6d499a901c2a62a5856a042130378be8ca
Author: Terence Yim <[email protected]>
Date:   2015-05-05T02:23:37Z

    (TWILL-69) Removed guava dependencies from twill-api and twill-common 
modules
    
    Following changes are backward incompatible:
    - TwillController no longer extends from Guava Service
      - No more start() method. stopAndWait() becomes terminate()
    - TwillRunnerService no longer extends from Guava Service
      - Only has the blocking start() and stop() for start and stop.
    - Classes moved from twill-common to twill-core, hence no long public
      - o.a.t.common.Services
      - o.a.t.common.ServiceListenerAdapter
      - o.a.t.common.CompositeService
      - o.a.t.common.DefaultResourceReport
    
    Modified all unit-tests and examples to use the new API

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to