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

Marco Descher commented on FELIX-4450:
--------------------------------------

I have set-up maven-scr-plugin to automatically work on all bundles in my repo. 
Even on bundles that don't have any @Component entries. Currently I have to add 
at least an import package org.osgi.service.component to satisfy the build on 
this exception.

I think it would be better, to just ignore the bundle if no such import is 
provided. I even work with pomless maven, so I would prefer this approach to 
de-activating the plugin for this specific bundle.


> failed to excurte scr-plugin, missing 
> org/osgi/service/component/annotations/Component
> --------------------------------------------------------------------------------------
>
>                 Key: FELIX-4450
>                 URL: https://issues.apache.org/jira/browse/FELIX-4450
>             Project: Felix
>          Issue Type: Bug
>          Components: SCR Tooling
>            Reporter: Reto Gmür
>
> I update a project (projectA) to use the org.osgi.service.component 
> annotations.
> Now dependent projects fail with the messages like the following:
> Failed to execute goal org.apache.felix:maven-scr-plugin:1.15.0:scr 
> (generate-scr-scrdescriptor) on project silklinking-service: Execution 
> generate-scr-scrdescriptor of goal 
> org.apache.felix:maven-scr-plugin:1.15.0:scr failed: A required class was 
> missing while executing org.apache.felix:maven-scr-plugin:1.15.0:scr: 
> org/osgi/service/component/annotations/Component
> if and only if:
> - they depend on projectA and the dependency is explicit in the pom 
> (transitive dependency isn't enough)
> - they use a version of the scr plugin more recent than 1.7.4
> Surprisingly the error occurs even if I add 
> org.apache.felix.scr.ds-annotations:1.2.4 as a dependency to the dependent 
> project.



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

Reply via email to