You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Philipp Ottlinger (JIRA)" <ji...@apache.org> on 2019/02/12 09:27:00 UTC
[jira] [Closed] (TAMAYA-381) Wrong service definitions that result
in ClassNotFoundException
[ https://issues.apache.org/jira/browse/TAMAYA-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philipp Ottlinger closed TAMAYA-381.
------------------------------------
Resolution: Fixed
> Wrong service definitions that result in ClassNotFoundException
> ---------------------------------------------------------------
>
> Key: TAMAYA-381
> URL: https://issues.apache.org/jira/browse/TAMAYA-381
> Project: Tamaya
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.4-incubating
> Environment: Ubuntu
> Karaf 4.1.5
> Reporter: Christian Niehues
> Priority: Major
> Fix For: 0.4-incubating
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In current version there are some service definitions pointing to unknown classes that result in a ClassNotFoundException from OSGIServiceLoader.
>
> These are the classes not found:
> {code}
> org.apache.tamaya.core.internal.DefaultConfiguration
> org.apache.tamaya.core.internal.CoreConfigurationContextBuilder
> org.apache.tamaya.core.internal.ConfigValueEvaluator
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)