[ 
https://issues.apache.org/jira/browse/FELIX-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132523#comment-15132523
 ] 

J.W. Janssen commented on FELIX-5177:
-------------------------------------

My java info:
{{[jawi@machine:felix-trunk/dependencymanager (trunk)]$ java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)}}

I'm running the same steps as you, only using the gradle-wrapper in the project 
root.

Looking into the test-results, I see the following error:
{{
  <testcase name='testWithOneAvailableExtraDependency' time='0.5' 
classname='org.apache.felix.dm.lambda.itest.MultipleExtraDependenciesTest'>
    <error 
type='java.lang.IllegalStateException'><![CDATA[java.lang.IllegalStateException:
 Can'f find lambda method name (Please check you are using javac -parameters op
tion).
 at 
org.apache.felix.dm.lambda.impl.Helpers.getLambdaParameterName(Helpers.java:64)
 at 
org.apache.felix.dm.lambda.impl.ComponentBuilderImpl.lambda$properties$131(ComponentBuilderImpl.java:224)
 at 
org.apache.felix.dm.lambda.impl.ComponentBuilderImpl$$Lambda$42/1089418272.accept(Unknown
 Source)
}}


> Support injecting configuration proxies
> ---------------------------------------
>
>                 Key: FELIX-5177
>                 URL: https://issues.apache.org/jira/browse/FELIX-5177
>             Project: Felix
>          Issue Type: Improvement
>          Components: Dependency Manager Runtime
>            Reporter: J.W. Janssen
>         Attachments: FELIX-5177.patch
>
>
> DM supports mandatory configurations, but does not allow anything other than 
> a dictionary to be passed to the callback. In other DI frameworks (like DS) 
> it is possible to use type-safe configurations and let those be injected 
> instead of plain dictionaries.
> It would be great if DM also would support this, as it would remove lots of 
> configuration boiler plate code from our projects.



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

Reply via email to