[
https://issues.apache.org/jira/browse/TAMAYA-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758072#comment-16758072
]
William Lieurance commented on TAMAYA-381:
------------------------------------------
Hey Christian. I think I found what happened. A couple of commits like [this
one|https://github.com/apache/incubator-tamaya/commit/15f7cbbb3ffac1e4cd2d2de0aabbb380fbc0b378#diff-5c96f770bdf95eae3b245e2124ff6241]
and [this
one|https://github.com/apache/incubator-tamaya/commit/7917a9f38e4087814ea1987395cb48edff7dfe2c#diff-29ace93c1407a2f2e27aff9858f7b20a]
moved some of the classes around but didn't update the service definitions.
I'm interested in what you ran that showed you that they were wrong; clearly
there's something missing from the tests around that.
If you could take a look at
[https://github.com/peculater/incubator-tamaya/tree/TAMAYA-381-service-def-movement]
and see if it works better for you I'd appreciate it.
> 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
>
> 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:
> org.apache.tamaya.core.internal.DefaultConfiguration
> org.apache.tamaya.core.internal.CoreConfigurationContextBuilder
> org.apache.tamaya.core.internal.ConfigValueEvaluator
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
