You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2011/05/04 15:21:03 UTC
[jira] [Created] (KARAF-608) Allow for multi-stage boot features
installation
Allow for multi-stage boot features installation
------------------------------------------------
Key: KARAF-608
URL: https://issues.apache.org/jira/browse/KARAF-608
Project: Karaf
Issue Type: Improvement
Affects Versions: 2.2.0, 2.1.5
Reporter: Gert Vanthienen
Fix For: 2.1.6, 2.2.2, 3.0.0
Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-608:
---------------------------------------
Fix Version/s: (was: 2.2.7)
(was: 3.1.0)
3.0.0
2.2.6
I would like to address this issue in Karaf 2.2.6. If it's the only pending one, I will move it ;)
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.6, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-608:
---------------------------------------
Component/s: karaf-features
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-features
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.1.6, 2.2.3, 3.0.0, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jamie goodyear (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear updated KARAF-608:
---------------------------------
Fix Version/s: (was: 2.2.6)
2.2.7
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.7, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-608:
------------------------------------------
Assignee: (was: Jean-Baptiste Onofré)
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.3.0, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Achim Nierbeck (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244644#comment-13244644 ]
Achim Nierbeck commented on KARAF-608:
--------------------------------------
I think since it's an improvement and we really should get a 2.2.6 out we should bump it to a 2.2.7.
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.6, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-608:
---------------------------------------
Fix Version/s: (was: 2.3.0)
(was: 3.1.0)
3.0.0
2.3.1
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.3.1, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
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
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear updated KARAF-608:
---------------------------------
Fix Version/s: (was: 2.2.2)
2.2.3
Changed fix version.
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.1.6, 2.2.3, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029203#comment-13029203 ]
Gert Vanthienen commented on KARAF-608:
---------------------------------------
Since we're going to base ServiceMix 4.4.0 on Karaf 2.2.x, I don't mind putting in some extra effort myself to backport that change to the karaf-2.2.x branch since that will make our lives a bit easier on the ServiceMix end.
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.1.6, 2.2.2, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-608:
---------------------------------------
Fix Version/s: (was: 2.2.6)
2.2.7
Assignee: Jean-Baptiste Onofré
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.7, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jamie goodyear (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119218#comment-13119218 ]
Jamie goodyear commented on KARAF-608:
--------------------------------------
Bumping out to 2.2.5.
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-features
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.5, 3.0.0, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Tuomas Kiviaho (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242245#comment-13242245 ]
Tuomas Kiviaho commented on KARAF-608:
--------------------------------------
I hope that URL protocol issue solution mentioned in KARAF-918 would also make it possible to get rid of CustomBundleURLStreamHandlerFactory that is used in the maven plugin. Currently the maven plugin registers this one to make feature service's url resolution work. Problem is that there is no proper way to unset it and it will be delivered across maven plugins from then on (a.k.a. leaking the classloader). If I understood correctly the idea is to use URL stream handler service instead. I think this solution could be mimicked on maven plugin side as well by inspecting Pax URL manifests for exported services for instance. Making use of ServiceLoader would be cleaner and simpler approach but I don't think that Pax URL currently supports this.
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.6, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Christian Schneider (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated KARAF-608:
--------------------------------------
Fix Version/s: (was: 3.0.0)
3.1.0
Moving to 3.1. Feel free to move back if you think this is essential for 3.0
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.3.0, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider reassigned KARAF-608:
-----------------------------------------
Assignee: Christian Schneider
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Assignee: Christian Schneider
> Fix For: 2.3.1, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
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
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jamie goodyear (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear updated KARAF-608:
---------------------------------
Fix Version/s: (was: 2.2.5)
2.2.6
Bumping out to 2.2.6.
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-features
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.6, 3.0.0, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jamie goodyear (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear updated KARAF-608:
---------------------------------
Fix Version/s: (was: 2.2.4)
2.2.5
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-features
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.5, 3.0.0, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear updated KARAF-608:
---------------------------------
Fix Version/s: (was: 2.1.6)
Removing the 2.1.6 fix version -- the 2.1.x line is coming to EOL.
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-features
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.3, 3.0.0, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider resolved KARAF-608.
---------------------------------------
Resolution: Fixed
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
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
[jira] [Commented] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461654#comment-13461654 ]
Christian Schneider commented on KARAF-608:
-------------------------------------------
I thought a lot about a way to achieve the desired behaviour without staged boot features but found no working till now. So I will implement it like described.
The problem are the obr and the url handlers. Both are already needed when loading the bundles. So I think the easiest way to make sure both are loaded before bundles that need them is to load these features as a first stage. I am still not sure this is really the best solution but I found no better till now. Any ideas?
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Assignee: Christian Schneider
> Fix For: 2.3.1, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
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
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Christian Schneider (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated KARAF-608:
--------------------------------------
Fix Version/s: (was: 3.0.0)
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.6, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jamie goodyear (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227529#comment-13227529 ]
Jamie goodyear commented on KARAF-608:
--------------------------------------
Bumping out to 2.2.7
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.6, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear updated KARAF-608:
---------------------------------
Fix Version/s: (was: 2.2.3)
2.2.4
Bumping out to 2.2.4.
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-features
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.4, 3.0.0, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-608:
---------------------------------------
Fix Version/s: 3.1.0
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.1.6, 2.2.3, 3.0.0, 3.1.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-608:
---------------------------------------
Fix Version/s: (was: 2.2.7)
2.3.0
As it's a new feature/enhancement, I move it to Karaf 2.3.0 (2.2.7 is now only bug fixes release).
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.3.0, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029179#comment-13029179 ]
Jean-Baptiste Onofré commented on KARAF-608:
--------------------------------------------
It could be interesting indeed, but I think it should be done only on 3.0.0. If it's not painful, we can see to merge that on 2.2.2.
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.1.6, 2.2.2, 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-608) Allow for multi-stage boot features
installation
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated KARAF-608:
--------------------------------------
Fix Version/s: (was: 2.3.1)
Only implemented on trunk till now
> Allow for multi-stage boot features installation
> ------------------------------------------------
>
> Key: KARAF-608
> URL: https://issues.apache.org/jira/browse/KARAF-608
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.1.5, 2.2.0
> Reporter: Gert Vanthienen
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> Currently, all boot features specified are installed in a single go: all the bundles get installed, resolved and then afterwards get started. This works fine for most features, but there are a few scenarios where it would be nice to allow installing the boot features in a few independent batches.
> One example is ServiceMix' use of OBR in the features. You can install OBR support through a feature, but it needs to be installed before resolving the other features to allow the Features' OBR Resolver support to kick in. We have now worked around this in ServiceMix by adding the OBR feature's bundle to the startup.properties file, but it would be nice to have a simpler solution.
> Another example is a feature that include a war: url for adding web applications. That requires the war feature to be installed and started before attempting the installation of the web application feature.
> We could e.g. allow adding parentheses to group parts of the boot features that need to be installed in a single batch. Something like (obr,war),activemq,cxf,camel,jbi could install the 'war' and 'obr' feature in a first batch and the do the rest as usual.
--
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