You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2012/12/12 12:11:22 UTC
[jira] [Created] (FELIX-3815) Maven SCR Plugin does not correctly
set specVersion to 1.1 if bind method with two parameters are used (OSGi
Comp 4.2 $112.3.1)
Konrad Windszus created FELIX-3815:
--------------------------------------
Summary: Maven SCR Plugin does not correctly set specVersion to 1.1 if bind method with two parameters are used (OSGi Comp 4.2 $112.3.1)
Key: FELIX-3815
URL: https://issues.apache.org/jira/browse/FELIX-3815
Project: Felix
Issue Type: Bug
Components: Maven SCR Plugin
Affects Versions: maven-scr-plugin-1.9.0
Reporter: Konrad Windszus
The following code leads to an error in Eclipse
@Component()
public class DummyService {
@Reference(referenceInterface = ResourceResolverFactory.class, cardinality = ReferenceCardinality.OPTIONAL_MULTIPLE, policy = ReferencePolicy.DYNAMIC)
List<ResourceResolverFactory> factories;
protected void bindFactories(final ResourceResolverFactory factory, final Map properties) {
}
protected void unbindFactories(final ResourceResolverFactory factory) {
}
}
The following error will appear in Eclipse:
@Reference : Missing method bind for reference factories (org.apache.felix:maven-scr-plugin:1.9.0:scr:generate-scr-descriptor:process-classes) vanishes.
Only if specVersion=1.1 is explicitly set the error vanishes.
If built with Maven, the error will not appear and the maven-scr-plugin will automatically create the XML with the right specVersion 1.1
Seems that the version detection mechanism differs in regular Maven build and built triggered from m2e.
--
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