[
https://issues.apache.org/jira/browse/FELIX-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322224#comment-16322224
]
Carsten Ziegeler commented on FELIX-5694:
-----------------------------------------
There are two different plugins: the maven-scr-plugin and the
maven-bundle-plugin. If you're using the maven-scr-plugin then bnd is not used
and we could change the code.
However, the easier (and better) option is to not use the maven scr bundle and
just use the maven bundle plugin which is also capable of processing the
annotations and then bnd is used which (I hope) is already using the name
attribute for the name of the XML file
> maven-scr-plugin use service name property as filename.xml
> ----------------------------------------------------------
>
> Key: FELIX-5694
> URL: https://issues.apache.org/jira/browse/FELIX-5694
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Reporter: Stefan Triller
> Labels: features, maven
>
> Hi,
> the current maven-scr-plugin uses the fully qualified class name as a name
> for the xml file that will contain the generated service description.
> Unfortunately the Eclipse IDE uses the service name as the name for the xml
> file, i.e. for
> {code:java}
> package org.mycompany;
> @Component(name = "org.topic.myservice")
> public class MyClassName {
> {code}
> it would create "org.topic.myservice.xml" inside the OSGI-INF directory.
> At the moment your maven-scr-plugin would create
> "org.mycompany.MyClassName.xml".
> if you use both, maven and the Eclipse IDE on the same workspace this will
> result in duplicate service descriptions.
> Would it be possible for you to implement a new option that allows for using
> the service name (if set) as a name for the generated xml file?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)