[
https://issues.apache.org/jira/browse/FELIX-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367581#comment-15367581
]
Stefan Seifert commented on FELIX-5116:
---------------------------------------
the plugin is only there to include SCRDescriptorBndPlugin - so i cannot only
use the "new" OSGi SCR annotations, but also the "old" ones from the felix
project. you need it only if you use the old ones from the package
{{org.apache.felix.scr.annotations}}.
the explicit configuration of scrLocation is only required for the manifest
goal, any only for the unit tests. if you do not configure it you will still
get the correct files in OSGI-INF in your JAR file - bndlib takes care of this.
but only in the JAR file and not in the filesystem in the classes path - and
thus not reachable for the unit tests. the explicit manifest goal generated
them during processing the classses and the scrLocation property tells it where
to put them so the unit tests can find them. it took me some time as well to
get this right.
> Dump SCR component definitions broken
> -------------------------------------
>
> Key: FELIX-5116
> URL: https://issues.apache.org/jira/browse/FELIX-5116
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-3.0.0
> Reporter: Stefan Seifert
> Fix For: maven-bundle-plugin-3.1.0
>
> Attachments: FELIX-5116.patch
>
>
> the feature to optionally dump SCR component definitions generated by bnd to
> the output classes folder introduced in FELIX-3324 is broken ins
> maven-bundle-plugin 3.0.0 and 3.0.1 - the associated code is never called
> when generating the bundle or manifest.
> the attached patch fixes this and enabled the behavior for both manifest and
> bundle goals.
> this feature is imporant for unit test support in IDEs, e.g. for
> https://sling.apache.org/documentation/development/osgi-mock.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
