You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by CMoH <gi...@git.apache.org> on 2017/07/27 17:18:40 UTC

[GitHub] karaf pull request #331: Fix karaf scheduler interface abstraction leak on e...

GitHub user CMoH opened a pull request:

    https://github.com/apache/karaf/pull/331

    Fix karaf scheduler interface abstraction leak on exceptions

    Wrap quartz SchedulerException in SchedulerError instead of using the
    private exception class in the scheduler API.
    
    This fixes wiring errors in service clients when using the scheduler interface, since class `org.quartz.SchedulerException` is not exported by scheduler-core bundle.

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

    $ git pull https://github.com/CMoH/karaf fix-scheduler-abstraction-leak

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

    https://github.com/apache/karaf/pull/331.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 #331
    
----
commit 6a548d83f4977f383524637d2f129b339c6578a3
Author: Ciprian Ciubotariu <ch...@gmx.net>
Date:   2017-07-27T17:13:32Z

    Fix karaf scheduler interface abstraction leak on exceptions
    
    Wrap quartz SchedulerException in SchedulerError instead of using the
    private exception class in the scheduler 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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] karaf pull request #331: Fix karaf scheduler interface abstraction leak on e...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/karaf/pull/331


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---