[ 
https://issues.apache.org/jira/browse/FELIX-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved FELIX-6142.
-----------------------------------
    Resolution: Fixed

you're right - documentation is fixed:
http://felix.apache.org/documentation/faqs/apache-felix-bundle-plugin-faq.html#use-scr-metadata-generated-by-bnd-in-unit-tests

> Documentation on maven-bundle-plugin
> ------------------------------------
>
>                 Key: FELIX-6142
>                 URL: https://issues.apache.org/jira/browse/FELIX-6142
>             Project: Felix
>          Issue Type: Improvement
>            Reporter: Ben Zahler
>            Assignee: Stefan Seifert
>            Priority: Minor
>
> On 
> [http://felix.apache.org/documentation/faqs/apache-felix-bundle-plugin-faq.html,]
>  it is documented on how to include the SCRDescriptorBndPlugin with the 
> following instruction:
> <configuration>
>    <instructions>
>    <!-- Support parsing of maven-scr-plugin annotations through the 
> felix.scr.bnd plugin -->
>  
> <_plugin>org.apache.felix.scrplugin.bnd.SCRDescriptorBndPlugin;destdir=${project.build.outputDirectory};
>   </_plugin>
>    </instructions>
> </configuration>
> However, it took me a bit more than just that:
> 1. I had to include the dependecy to the plugin inside the 
> maven-bundle-plugin section:
> <dependencies>
>   <dependency>
>      <groupId>org.apache.felix</groupId>
>      <artifactId>org.apache.felix.scr.bnd</artifactId>
>      <version>1.9.4</version>
>    </dependency>
>  </dependencies>
> 2. I had to remove the final semicolon of this config:
> destdir=${project.build.outputDirectory}; 
> With this semicolon, I had the following message in my mvn build:
> Header contains name field after attribute or directive: null from 
> org.apache.felix.scrplugin.bnd.SCRDescriptorBndPlugin;destdir=/Users/benzahler/Documents/code/repos/reponame/apps/sites/bundle/target/classes;.
>  Name fields must be consecutive, separated by a ';' like a;b;c;x=3;y=4
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to