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

Jochen Fliedner commented on FELIX-2892:
----------------------------------------

The problem is this preceeding identification of the information kept in the 
Source objects collection. This is done on the - or an aggregation of? - source 
folder(s) using "project.getCompileSourceRoots().iterator()".
Class names are identified and in that some assumptions are hardcoded that are 
feasable only for Java sources:
- that the eventual classes fqns always corresponds with the folder structure 
and the file name of the sources
- that there is a "java" file extension
When locally in the code i switch to "project.getBuild().getOutputDirectory()" 
and assume a file extension of length 5 - like in ".class" - to be tossed, it 
basically works fine. So obviously you can always use such assumptions at the 
output dir with its folder structure and class files.
Especially with Scala there are some regarding problems like you can code 
multiple packages and types within one source file, but after compilation that 
should be fine.
Generally it would not be necessary to have any source folders involved for the 
nature of the thing that is to be accomplished here, even when it adheres to 
maven best practices to do so.
                
> Get SCR annotations to work with Scala
> --------------------------------------
>
>                 Key: FELIX-2892
>                 URL: https://issues.apache.org/jira/browse/FELIX-2892
>             Project: Felix
>          Issue Type: Improvement
>          Components: Maven SCR Plugin
>            Reporter: Reto Bachmann-Gmür
>
> Currently the maven scr plugin doesn't work with scala, teh main reason for 
> this is that the annotation have only source scope and the adding of 
> bind-methods happe on a source rather than a bytecode level.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to