You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Lars Heinemann (JIRA)" <ji...@apache.org> on 2011/01/18 08:22:44 UTC
[jira] Created: (SM-2038) add osgi header to
manifest
add <Bundle-Description> osgi header to manifest
------------------------------------------------
Key: SM-2038
URL: https://issues.apache.org/jira/browse/SM-2038
Project: ServiceMix
Issue Type: Improvement
Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
Affects Versions: 4.0
Reporter: Lars Heinemann
To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
{code}
In the pom:
<description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
In the Felix plugin configuration:
<Bundle-Description>${project.description}</Bundle-Description>
{code}
The header has been already added to:
- servicemix-utils
- smx4/features
- smx4/nmr
- components
But the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Commented] (SM-2038) add osgi header
to manifest
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041577#comment-13041577 ]
Jean-Baptiste Onofré commented on SM-2038:
------------------------------------------
I checked the descriptor and added OSGI-INF/bundle.info in ServiceMix Utils:
Committing to https://svn.apache.org/repos/asf/servicemix/utils/trunk ...
M pom.xml
A src/main/resources/OSGI-INF/bundle.info
Committed r1129667
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
> Assignee: Jean-Baptiste Onofré
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-2038) add osgi header to
manifest
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984211#action_12984211 ]
Jean-Baptiste Onofré commented on SM-2038:
------------------------------------------
First bundles which use the "new" Karaf OSGI-INF/bundle.info: revision 1061317.
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-2038) add osgi header to
manifest
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-2038:
-------------------------------
Description:
To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
{code}
In the pom:
<description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
In the Felix plugin configuration:
<Bundle-Description>${project.description}</Bundle-Description>
{code}
The header has been already added to all poms, but the description needs attention everywhere!
was:
To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
{code}
In the pom:
<description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
In the Felix plugin configuration:
<Bundle-Description>${project.description}</Bundle-Description>
{code}
The header has been already added to:
- servicemix-utils
- smx4/features
- smx4/nmr
- components
But the description needs attention everywhere!
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-2038) add osgi header to
manifest
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983127#action_12983127 ]
Gert Vanthienen commented on SM-2038:
-------------------------------------
Added descriptions for all the NMR bundles in http://svn.apache.org/viewvc?view=revision&revision=1060269
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SM-2038) add
osgi header to manifest
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983150#action_12983150 ]
Lars Heinemann edited comment on SM-2038 at 1/18/11 8:27 AM:
-------------------------------------------------------------
added description for smx4 features.
added description for components.
Servicemix-Utils already had a description.
was (Author: lhein):
added description for smx4 features.
Servicemix-Utils already had a description.
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-2038) add osgi header to
manifest
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986323#action_12986323 ]
Jean-Baptiste Onofré commented on SM-2038:
------------------------------------------
ServiceMix Bundles now contain the OSGI-INF/bundle.info entry: revision 1063183.
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
> Assignee: Jean-Baptiste Onofré
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-2038) add osgi header to
manifest
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned SM-2038:
----------------------------------------
Assignee: Jean-Baptiste Onofré
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
> Assignee: Jean-Baptiste Onofré
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-2038) add osgi header to
manifest
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984140#action_12984140 ]
Jean-Baptiste Onofré commented on SM-2038:
------------------------------------------
Regarding KARAF-403, I'm gonna:
- update the bundles-pom to handle filtered resource
- add OSGI-INF/bundle.info resource that will be read by Karaf
- the <description/> will contain only the bundle synopsis
The same change will be performed on NMR, components, etc.
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-2038) add osgi header to
manifest
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984670#action_12984670 ]
Jean-Baptiste Onofré commented on SM-2038:
------------------------------------------
Usage of ASCII formatting (bold and color): revision 1061726.
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-2038) add osgi header to
manifest
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984799#action_12984799 ]
Jean-Baptiste Onofré commented on SM-2038:
------------------------------------------
Resuming OSGI-INF/bundle.info addition: revision 1061880.
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-2038) add osgi header to
manifest
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983653#action_12983653 ]
Jean-Baptiste Onofré commented on SM-2038:
------------------------------------------
I add it into ServiceMix Bundles.
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-2038) add osgi header to
manifest
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983150#action_12983150 ]
Lars Heinemann commented on SM-2038:
------------------------------------
added description for smx4 features.
Servicemix-Utils already had a description.
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-2038) add osgi header to
manifest
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983734#action_12983734 ]
Jean-Baptiste Onofré commented on SM-2038:
------------------------------------------
I began to add enhanced Bundle-Description is ServiceMix Bundles: revision 1060829.
I keep on running :)
> add <Bundle-Description> osgi header to manifest
> ------------------------------------------------
>
> Key: SM-2038
> URL: https://issues.apache.org/jira/browse/SM-2038
> Project: ServiceMix
> Issue Type: Improvement
> Components: samples, servicemix-bean, servicemix-bpe, servicemix-camel, servicemix-common, servicemix-components, servicemix-core, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-truezip, servicemix-utils, servicemix-validation, servicemix-vfs, servicemix-web-console, servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 4.0
> Reporter: Lars Heinemann
>
> To make our bundles more self-documenting we should add the osgi header "Bundle-Description" to the manifest of our bundles. This header should be filled with the pom description. If the description is not existing or not sufficient it should be added/improved as well.
> {code}
> In the pom:
> <description>PUT IN A SUFFICIENT DESCRIPTION HERE WHICH DESCRIBES THE FEATURES THIS BUNDLE OFFERS...</description>
> In the Felix plugin configuration:
> <Bundle-Description>${project.description}</Bundle-Description>
> {code}
> The header has been already added to all poms, but the description needs attention everywhere!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.